lunes, 17 de marzo de 2014

I quit! 10 things that drove me out of IT (TechRepublic)

By  in 10 Things,                                              March 16, 2014

After six years of working as a remote support tech for a managed service provider, Jack Wallen threw in the towel. If you've ever been tempted to quit IT, his reasons may sound familiar. 
hero
Image: iStockphoto.com/IvanBastien
Some people assume that the world of PC support is a glamorous, Sheila E sort of life. After all, it's technology, geeking out all day long. What's not to love?

Famous last words.
For what seemed like an eternity, I served as a support tech for a managed service provider (MSP). Starting the job, I had no idea what I was getting into. As the saying goes, "If I knew then what I know now…." Would I have stepped foot into the world of remote support? It's hard to say. What is not so hard to say is why I eventually gave up being a support technician. In fact, I can give you 10 reasons why.

1: Stress

This is the number one reason why I left. If you've never experienced the levels of stress associated with managed service providers, you're in for a real treat. You have (possibly) hundreds of clients calling in all day to report their computers "aren't working." The queue lines up with people who can't get their work done because "you haven't fixed their problems." It's disaster management and triage all day and it never lets up.

2: Pay

The pay for an MSP engineer is not what you'd think it would be. I nearly exploded with laughter every time I heard a client say, "That's why you get paid the big bucks." I wanted to say, "You probably get paid more than I." But I refrained. Every time. The truth is, the pay just wasn't enough to offset the high levels of stress and frustration. It made more sense to move on.

3: Printers

Nearly half of what I did all day was fix printers. That's how I came to the conclusion that the very foundation of printing is broken. I never signed up to be a printer technician and would feel my blood boil every time I saw a support request come through that said, "My printers stopped printing!"

4: Ignorance

I hate to be one of "those people," even momentarily. Still, the levels of ignorance I dealt with on a daily basis were staggering. I was always professional, and I tried to be patient and kind. But fielding the same questions over and over — things as basic as, "What's a web browser?" — eventually wore me down.

5: Micromanaging

As a contract company, MSPs need their engineers working at 150 percent all day, every day, and each second must be accounted for and billed. So it's not surprising that they tend to micromanage the staff. Some people can handle this management technique. But it drove me mad to have someone breathing down my neck all day. There was also an avalanche of paperwork we had to do to ensure that we'd be covered in case of a disaster.

6: The pace

The world of PC support (especially of the remote flavor) can be boiled down to this: You have way too much to do, not enough time to do it, and not enough help to get it done. And as that workload piles up, you have angry clients who can't get their own work done. To accommodate this, you have to work at a pace you can't maintain for any length of time (which leads us back to #1: stress).

7: Windows

I've always been upfront about my opinion that Microsoft Windows is the reason tech support is so busy. I mentioned that half of my job was fixing printers. The other half seemed to be malware and viruses. Every day I fought the urge to blurt out, "If you used Linux or Mac, you wouldn't have these problems and you'd save a ton of money!" But I refrained. Every time. If you've experienced the stability and reliability of "the other platforms," you get this. You don't want to spend your day supporting Windows. You'd rather spend a portion of your day training users on another platform and watching them work happily ever after.

8: Multitasking madness

I am a multitasker. I often have two to three major tasks running at once. I'll be writing a tech piece, a work of fiction, and getting intense on social media. But the problem with working directly in IT is that you get your head buried in something you've been told is critical... only to be yanked from that task to do something like fix a printer for a CEO. You come back to the original task(s) and find your flow completely ruined and you're back to square one. This happens more often than not, and you lose a lot of work as a result.

9: The love of technology 

It can be tricky when your work intersects with something you're passionate about. For me, technology is one such passion. But having to deal with tech issues (often caused by user-error or platform inadequacies) day in and day out was starting to ruin it. I even began to hate it. That caused serious problems for me, as I had to go home and toil away in front of a computer to create works of fiction, which is something that usually brings me great joy. It wasn't until I left the support industry that I regained my love for technology.

10: Burnout

There is no avoiding this. You will burn out. The pace and stress tend to remain neck and neck in the race to subvert your sanity. Working support will eventually take you down. And (at least for me), you'll find yourself carrying that stress home with you. You'll go through periods where that stress doesn't seem to want to wash down the drain and it turns you inside out. For me, that was too big a price to pay.

The last straw

Not every company and not every person is cut from the same cloth. There are those out there who will gladly tolerate what, in the end, sent me packing. I am also not pointing any fingers at any one company. Ultimately, the killing blow was my own lack of resilience and my inability to keep up with the choking pace of the managed service provider industry.
Jack Wallen is an award-winning writer for TechRepublic and Linux.com. He’s an avid promoter of open source and the voice of The Android Expert. For more news about Jack Wallen, visit his website getjackd.net.

martes, 11 de marzo de 2014

The dark side of venture capital: Five things startups need to know

By                                                               March 10, 2014, 5:34 AM PST
Venture capital funding is a great tool for entrepreneurs, but its implications are often not fully understood. Here's what VC-seekers need to know. 
evilbankmoney.jpg
Image: iStockphoto/darak77
Nearly $27 billion dollars was invested by venture capitalists in 2012. That $27 billion was invested across 3,723 deals, making the average deal hover at a little over $7 million.
While that number may seem staggering to many people, it's about average for VC investments made since the dot com bubble burst between 2000 and 2001, according to the National Venture Capital Association (NVCA). Yes, the economic impact of the dot com bubble was horrendous, but it did spawn a renewed sense of innovation in startup development.
Companies are running leaner than ever, and because of that VCs are more willing to invest in companies who don't pride themselves on their burn rate. Still, raising venture capital funding can be a risky business if you aren't realistic about what to expect.
Here are some things to think about if you are considering raising your first round.

1. Statistically, you will fail

The venture capital investment process is a complicated one and potential companies are vetted thoroughly before they are committed to. With that being said, just because your company is backed by a major VC you aren't guaranteed success.
Think about those 3,723 deals that happened in 2012. In that same year there were only 49 IPOs and 449 mergers and acquisitions (M&A) deals. Granted, those exits came from companies that were invested in probably a decade ago, it is still an interesting ratio to consider.
Micah Rosenbloom, a venture partner at Founders Collective, said that historically, only one out of every 10 companies that a firm invests in with a given fund will be successful. That's not to say that all of the remaining companies will fail, though. According to Tomasz Tunguz, a partner at Redpoint Ventures, "Typical portfolio company failure rates across the industry defined as either shutdowns or returning capital are roughly 40%-50%."
This isn't to discourage hopeful founders that are seeking capital, but to ground your expectations in reality. Besides, entrepreneurship is about having the courage to fail, right? The fact that you are more likely to fail is a fact of life for venture-backed companies, it is not an expectation for the VCs making the investment.
"You never invest in a company thinking that it will fail," Tunguz said.
A VC investment in your company does not guarantee success, but it does mean you have someone in your corner who believes you have what it takes to make this thing work. Once you have a VC in your corner, you have to make sure you are in sync on what it will take to make this a worthy investment. More importantly, you have to know how long it will take for this investment to pay off.

2. There is a timeframe for ROI

"Typical venture funds are structured as 10 year commitments for the limited partners who invest in the fund," Tunguz said.
Venture capital firms are ten-year vehicles for investors, but that doesn't mean that all companies will be ten years old when they return on the investment. Rosenbloom mentioned that initial investments are made in the first three years. After the portfolio has been establish, a firm will typically make follow-on investments over the remainder of the fund's lifecycle.
Ten years may sounds like a long time, but you have to consider how long companies like Coca-Cola have been around (since 1892) and some companies that were started in the 2000s have a comparable valuation to Coke. Founders Collective is usually the first institutional round in a company, and Rosenbloom said that they aren't looking for the next cool invention.
"As a venture capital firm, we are not in the business of funding inventors or inventions, we are in the business of funding fast-growing companies," Rosenbloom said.
Considering the first three years as initial investments, a company could only have seven years to "make it." Some VCs, like Rosenbloom, consider seven years the average age for ROI, and the data from NVCA supports that claim.
The NVCA reported in their 2013 Yearbook that, of the 49 IPOs that happened in 2012, the median age for IPO was 7 years old and the mean age for a company to IPO was 8 years old. While some have argued that it is taking longer for startups to mature, Tunguz argues, "The gestation period will likely fall some because of the tremendous exit activity in M&A and IPOs in the last 24 months."
To help you make it through the whirlwind of growth that can happen after an investment, you have to know how much capital you need and when you need it.

3. You can take too much funding

"All too often, entrepreneurs will think of raising a Series A round from a reputable VC as the end goal and don't think they can be successful unless they do so. So they reprioritize raising capital over building a valuable product or service and usually end up asking for too much money too soon which ends up in a failed fundraising attempt or a raise on bad terms for the entrepreneur," said Hrach Simonian, a principal at Canaan Partners.
As I mentioned in a previous article, knowing how much money you need can make all the difference in your venture capital experience. It starts by understanding how much money you need and only raising that much money. Raising too much money can force entrepreneurs to make decisions they aren't ready to make.
"If you raise too much money, you have to swing for the fences," Rosenbloom said.
You want the amount of money you raise to coincide with the benchmark you are trying to hit. If you don't have a specific benchmark in mind (which you really should), a good rule of thumb is to consider the amount of capital it takes to sustain your operations for 18 months, then add 25-50 percent for added flexibility and seek to raise that amount of money.
Tunguz said that raising too much capital is far from the gravest sin to be committed by an entrepreneur, "But having a huge sum of money in the bank can entice founders to dramatically increasing burn rate or diffuse the company's energy among many projects. It can be challenging to maintain the same execution discipline created by the scarcity of capital when the bank account is overflowing."
Another risk of raising too much capital is setting the bar too high for your exit. By doing so you will run the risk of not being able to grow into the expectation that was set by raising a large amount of money.
Remember to raise enough to get yourself to the next stage where you can assess whether or not you need to raise more money. Keep in mind that once you choose a firm and raise those funds, that VC will probably get a permanent seat on your board of advisors. Choose carefully, because you are usually stuck with that investor for good.

4. You can't fire your VC

Too many founders abdicate their due diligence when it comes to the firms they end up pitching. Each venture capital firm has its own general focus on specific sectors or verticals. Taking that to a more granular scale, each partner within each specific firm maintains investments in a focused area of expertise.
Founders typically don't appreciate the incentive structure on the side of the fund, which is based on the size and the dynamics of that fund. Understand how the fund makes money to determine if it is a good fit for you. The size of the fund will be a good determinant for whether or not your company will present a quality investment opportunity for the partners.
You have to think of your VC firm as another partner in your business.  This leads to one of the single most important aspects of your startup/VC relationship: Make sure your goals for your company line up with your VC's goals for his or her investment. By aligning your goals with those of your VC, you can help potentially avoid a disaster scenario.  
"The disaster scenario is that the founding team wants to do something different than the board," Tunguz said.  
The risk/reward curves are different for entrepreneurs than they are for VCs, and board members (including your VC) have a legal responsibility to take into account the goals of the investors. So, if your company is losing steam and an acquisition opportunity comes along that is in the best interest of your investors, they might push you to take it, even if it means you don't get paid.
But, of course, you can avoid all that potential heartache by not taking funding to begin with.

5. Failure isn't death

Micah Rosenbloom describes venture capital as jet fuel. If you want to drive somewhere 100 miles away, you'll probably drive there. If you want to get from New York to Los Angeles, you're going to have to fly, and you will need fuel to power that jet.
Venture capital gives you potential—the potential for major success and the potential to fail spectacularly. The good news here—the gospel of venture capital if you will—is that failure is not the end of the story if you play your cards right. Despite stereotypes, most VCs are actually looking to build relationships with entrepreneurs, not just make money off of them.
"The Valley is small, and life is long," Tunguz said.
According to Tunguz, when it comes to his work at Redpoint Venture, great relationships are the motivation, because even if you fail it's not the end of the world. What is much more important is how you fail and how transparent you are throughout the process. If you keep people informed when you hit a snag and ask for help with a problem, you can build trust with your investors.  
Venture capital investors want to know that you will be a good steward of the funds they placed under your control. If you can prove yourself a highly competent entrepreneur and someone who will push as hard as they can to make an idea work, failure will not mean the end of your career as an entrepreneur. At that point, even if you fail, past investors and people involved with your company will be far more likely to fund your next project if they trust the way you work.
As an entrepreneur, burning bridges is unwise. Treat people with respect to build social capital, but don't see them as just a resource either. Other than that, always remember that if you're going to fail, fail big and go down swinging.  
Conner Forrest is a Staff Writer for TechRepublic. He covers Google and startups and is passionate about the convergence of technology and culture.