Archive for the ‘Business’ category

Lingo

December 23rd, 2010
Look Who's Talking

Image via Wikipedia

We should probably re-calc those betas and update the capital structures before handing the final ATWACC to the client. Also, while an interest rate adder is non-standard for the CAPM, the yield curve is just too low to be believed by any regulatory commission.

It’s a non-trivial refactoring of dev which has the potential to spiderweb, which would then delay our push to staging. It might be better to just add simple affordances instead through a JQuery plugin.

The client is an interop providing level 3 access for click-to-call functionality. We should socialize this with X’s group to see if we might encounter any push back.

I’ve now worked at 3 different companies since college, each with it’s own language.  Each time I change jobs, I’m amazed by the disparate vernacular employed by each.

Enhanced by Zemanta

Coffee Talk

April 30th, 2010
Brown cup of coffee
Image via Wikipedia

I’m a big fan of meeting entrepreneurs for coffee. Now that I’m doing a lot more financial consulting, I find that it’s harder and harder to stay involved in the “scene”. People in this industry are mortally afraid of new technologies like twitter, blogging or web technologies, so sometimes I find myself straying from my startup roots.  Thats why I’m thankful for being able to work with AccelGolf, and that’s why I love to meet up with other startup guys.

Today, I had back to back meetings with some interesting guys at the Andala Cafe in central. First I met with Waldron Faulkner of GraphEdge who is working on his pivot and needed some marketing help and introductions. Waldron is a passionate guy who’s got a lot of work ahead of him, but isn’t afraid of it. Waldron inspires me because making those pivots is hard, and sometimes barreling ahead is the easiest thing to do, when in reality, it’s the worst thing you can do.

Next, I met with Dustin Dolginow of Atlas Ventures. Dustin’s a newbie to both Boston and the VC world, so he’s trying to get his feet under him. As coincidence might have it, he’s also a fellow Kansan – from my same town too! Startup guys please welcome him to Boston, and if you are interested in meeting a junior VC with the ear of some pretty powerful guys, let me know and I’ll put you in touch. Dustin inspires me because he’s in a whole new world and he’s attacking it with a vibrance and energy that we should all aspire to – and he’s a genuinely nice guy.

Ah coffee talk…

Reblog this post [with Zemanta]

HR Failures – Self Review Processes

April 20th, 2010
Frustration
Image by beau-foto via Flickr

Several friends of mine work at a nice boutique consulting firm in the Boston area which typically promotes everyone once a year depending on their performance.  As such, they are also in the midst of review season whereby their bosses will critique their performance and they, in turn, will also evaluate their performance.

The self-review packet is eleven pages, consisting of mostly prose responses whereby the writer will elaborate on their different core competencies and skill sets, preferably using examples from their project work. Each question has three parts, asking the writer to elaborate on: their successes, their challenges, and their goals for the future.

The reviewer, too, has to write about the reviewee, grading each of these criterion and carefully deciding on why or why not this person deserves a promotion.

The full review packet, mind you, is incredibly thorough – a ton of thought was clearly put into this process – and the self review packet, with due respect to it’s creators (who obviously labored intensively over it’s creation), sucks.

Why, pray tell does this process stink?

  1. There is a HUGE waste in productivity.  Each Self-Review packet takes on average over 5 hours to complete. And each review of this person takes another several hours (lets guesstimate 3), meaning that for each employee of the firm, 8 hours are spent on this. It’s a small firm, and only about 100 or so of the employees are reviewed, so that’s 800 man-hours of time. Each of these people also bill out at an hourly rate (for the most part), and I can tell you, those rates ain’t cheap. Starting employees are right around $200/hr, so let’s assume, conservatively, that the average rate is $250/hr for all employees. That means the firm will lose $200,000 from the process.
  2. The questions ask, nay, BEG for bullshit responses. When, for example, in a section on Self-Management, when a question asks if you are mature, responsible, understanding of project needs, what rational person in their right mind isn’t going to BS this? And if every response is BS, what do you think the likelihood of a quality actionable self-evaluation is? Not very high.
  3. Once you fill it out, nobody looks at it again. In fact, the only reason to keep old reviews is so that you can copy and paste entire sections from the last review into the new one! What’s the point of asking for goals for the next year, and then not comparing your results?
  4. It measures the wrong things. This process rewards generic, BS responses, while harming individuals who recognize they need to improve in certain areas. You need to be good, but not cocky, just enough above average to get that promotion, but don’t remind anyone of any flaws that you might have.  The point of a self-review is so that your bosses can see if your views of yourself are in any way different than their views of yourself. Any areas where there is a huge disconnect should be explored in greater detail. ie. If I think my Excel skills are piping hot, but my boss thinks I’ve got the Excel acumen of a 3rd grader, then that begs for action.

So what’s a better process?

Listen up people in HR, because it’s going to blow your mind. Less is more!

Any self review must take into account the 4 criticisms above. It must be:

  1. Short
  2. Elicit Truth
  3. Actionable
  4. Measure the right qualities

So here’s the ideal review process, IMO:

The reviewee will get a form with upwards of 10 different qualities, each with its own sliding scale from 1 to 10. This can be things like “Excel Skills”, “Presentation Skills”, “Client Interaction”, “Managing Employees”, etc., and the user will rank themselves 1 to 10.  They also should be required to mark 2 or 3 skills that they would like to improve upon over the next year. Lastly, there should be ONE (and only one), comment box which would allow someone to list the projects they worked on since the last review, and any thoughts about that specific project that they might have.

The reviewer will also get a form, with the sliding scale from 1 to 10 for each of the qualities of the reviewee. They will not know how the reviewee reviewed themselves, on each of the categories but they will be able to see the comment box with the projects and thoughts the individual had. They will then rank the reviewee, write a brief comment about the employee (project based comments) and then submit their review.

The HR department will then sift through all of these reviews and only look for 2 things:

  1. Quality: Is the reviewee below a certain threshold of quality (let’s say below a 5)?
  2. Perceived Differences: Are there differences between what the reviewer and reviewee’s scored?

Any score differences will necessitate further elaboration from the employee. Any employee that passes the quality threshold and the perceived differences threshold will pass directly through the system, and will be eligible for a promotion.

Let see if it matches up to the criticisms:

  1. It’s definitely short – a sliding scale, 3 check boxes, and a comment box…probably 45 minutes at most to fill out.
  2. It elicits truth through a bidding-like mechanism – the reviewee only is eligible immediately for a promotion if their scores are in line with their reviewers.
  3. It’s possibly actionable – by selecting 3 areas where you would like to improve, you can check your scores from last year to compare to this year.
  4. Measures the right qualities – this is more up to the different categories that are chosen by HR, but I believe that a ranking scale is far superior to a prose review.

What do you guys think? Where can the self evaluation be improved?

Reblog this post [with Zemanta]

TechStars startup AccelGolf and yours truly

March 24th, 2010
Image representing AccelGolf as depicted in Cr...
Image via CrunchBase

Since leaving WebNotes a few months ago, I’ve been on the lookout for another fun startup to help out with. For months, I was a networking whore, meeting as many of the best and brightest as I could in the Boston startup community. During my search, I was lucky enough to encounter William Sulinski, CEO and founder of AccelGolf, a recent TechStars graduate company.

As luck would have it, AccelGolf is in need of some marketing assistance, and William was kind enough to offer me the gig.  Over the next few months, I’ll be helping out with some strategic planning, implementation and customer development work.

I’m still keeping the day job for now,  but I’m thrilled to be working with another startup, especially one as well positioned as AccelGolf.

For those of you who haven’t heard of it, check out this great golf tool. It’s a cellphone app that functions as part rangefinder (so you always know your yardage), part statistics machine, allowing you to understand your game at a whole new level.

I’ll keep you guys posted on how things go.

Reblog this post [with Zemanta]

Waiting on hold, and other stupid things that I do

February 16th, 2010
Sprint Nextel

Image via Wikipedia

As a business owner, I would always wish that my customers or users would email me feedback regardless whether I asked for it. It’s nice to hear when you are doing things well, and its great (though not pleasant) to hear when you screw up. Screwing up allows you to fix things, and more often than not, your customers will thank you.

As such, I do stupid things, like wait on hold to make silly requests – like when Comcast didn’t offer CNBC, or Red Zone, or a whole host of other channels to subscribers in Cambridge, I called to request it (and waited for 30 minutes).  Lo-and-behold, 4 months later Comcast added these stations. Do I really believe that my feedback spurred the change? No. Do I believe that enough people called to complain? Yes, and that’s why I do these things – the marginal utility of my call.

That’s why I just sent an email to Sprint to request that they start carrying the Nexus One. They’ll probably ignore my one email, but maybe, just maybe, they’ll get enough requests to realize they have an opportunity. Maybe they’ll understand that the reason they’ve been bleeding so many customers is because to-date, they’ve offered an inferior product with no competitive advantage.  They are a me too player, which lags in innovation…so far.

If Sprint is serious about winning their customers back, that means leapfrogging their competition: actually deploying a 4G network instead of over-promising and under-delivering, and also deploying only top of the line handsets which could handle this network, handsets currently only found on ATT or Verizon or T-Mobile. High end used to be the bread and butter of Nextel before Sprint watered it down with crap…so I have hope that maybe, just maybe, Sprint will find its way.

Reblog this post [with Zemanta]

Thoughts on Elance – Outsourcing to India

February 15th, 2010
India

Image via Wikipedia

For the last 3 weeks, I’ve been working with a firm out of India to help me with the design of my financial planning site.  So far, things are going relatively well, but there have been some bumps along the way. For those of you interested, here’s what to look out for.

Elance, for those who don’t know, is a site that connects freelancers with people in need of professional work.  I was able to post some basic specs, and a whole host of firms were able to bid on this work.

Choosing a Contractor

This really is going to be highly dependent on what you are looking for (and will seem a little discriminatory).  Keep in mind that you get what you pay for, so the better developers are  going to cost you more than $20/hr. As per some basic discrimination, avoid all developers in the US who charge $20/hr or less -cost of living alone in the US is phenomenally high compared to developing countries such that a similarly priced US and foreign firm will tell you something about what you will get back.  And if you are looking for something extremely high quality, avoid India and Pakistan.  Developers from this region are looking to cut corners and put something out as quickly as possible, regardless of quality. Something you also need to consider will be your own technical and product management skills. If you haven’t overseen a developer before, you might want to consider shelling out some more moolah.

Elance also provides samples of work from each firm, customer reviews, and a skill-set testing system so you can get a basic idea of what each firm can do. Before choosing a firm, make sure that the firm has taken Elance’s tests (instead of self rating which obviously is going to lead to arbitrarily high scores), and has received high marks from previous customers.

So why did I choose India?

Because the developer had ton a TON of work previously completed via Elance and had received mostly positive reviews. Also, per my own advice, I am getting a very alpha version out as quickly as possible so that I can test before I spend too much money. I’ve spec’d out what I consider a minimum viable product for initial feedback, and only once I feel we’ve developed a sustainable idea will I find a higher quality firm (or co-founder). Moreover there’s something to be said about having worked with Indian firms before, and having worked extremely closely with a wide variety of highly skilled developers here in the States.

My dream firm was this studly Ukrainian team that unfortunately would have cost me about 3 times as much. They were responsive, technically savvy, and honest about their qualifications and time needs. Sadly, for now I need something cheap and dirty, and am willing to sacrifice quality for cost effectiveness.

The Bumps

So far, communication has been the largest issue so far.  After I first selected the firm, when my project was being handed over from the marketing team to the developers, the firm stopped responding. Flat, cold stopped responding. I basically had to threaten to take my work elsewhere before someone got back to me and a flurry of activity began.  Luckily, the initial mockups of the homepage were of high enough quality to justify sticking with them.

My other issue with communication is around dialogue. I’m used to asking developers a question and getting an answer with a few options as well as a recommendation. This doesn’t occur with the Indians – instead, I ask “would this navigation work better horizontally instead of vertically?” and a day later they just respond “we have changed the navigation tabs”.

My last issue is one of quality. You can tell that some of the aesthetics are rushed, and often I have to ask for 4 or 5 iterations before something looks like it should’ve the first time. The code looks clean enough so far, mostly because I think they are using 3rd party open sourced plugins.  I’ll see how the custom code ends up looking, and hopefully that will be clean as well.

Final Thoughts

I’ll definitely follow up on this after the project is done, but so far so good. Here’s what I’ve learned:

1) Micromanage, micromanage, micromanage: you have to be on top of these guys day in and day out. Every week begins with me asking what the plan for the week is, and then for every iteration I critique and immediately send back my feedback. Typically, I hate to micromanage as I think it is hugely inefficient, but this is one of the exceptions to the rule.

2) Everything takes twice as long as you plan for: the typical adage is that it should cost twice as much as well, but this is a fixed bid. We’ll see about how much follow on work costs.

3) Know EXACTLY what you want: You can’t assume that the firm will go above and beyond to wow you, so you must have your project perfectly specified and planned.

Reblog this post [with Zemanta]

Why I love “Tabatha’s Salon Takeover”

February 11th, 2010
A Facial mask.
Image via Wikipedia

Yes, you read that right. My testicles apparently didn’t show up for this post. Perhaps the snowstorm scarred them away, but regardless, today I watched a marathon of Tabatha. She’s this slender, brash Simon Cowell wannabe who takes over failing hair salons and turns them around in a week – and it’s a great crash course in business.  It’s a consulting biz and I highly recommend checking it out. Here are the ABCD’s of Tabatha.

Aesthetics Count
Your clients notice when your office is dirty (or website for that matter), and what they view should be pleasing to the eye.  It’s really incredible what good design can do, and Tabatha goes in and guts their salons for better version.

Be Professional
Personality is great, but if you aren’t professional, then your clients won’t respect you and you certainly won’t be able to charge premiums for your service. So far I’ve seen Tabatha demolish people who start arguments with coworkers or yell across the salon, wear unbecoming clothing, or treat their clients with disrespect.

Customer Service, Customer Service and, oh yeah, Customer Service
Get out of the backroom and start talking to your clients.  Welcome them, make them feel comfortable, entertain them, and understand them.

Don’t Suck
There’s no excuse for you to do something you suck at. If you offer a shoddy service, you deserve to fail, or in Tabatha’s case, be fired.

Reblog this post [with Zemanta]

Interview with Mark Pincus

February 4th, 2010
Mark Pincus
Image via Wikipedia

The NY Times has a great interview with Mark Pincus of Zynga. They’ve got a great process for running the company which he describes here:

Q. What else is unusual about how you run the company?

A. John Doerr [the venture capitalist] sold me on this idea of O.K.R.’s, which stands for objectives and key results. It was developed at Intel and used at Google, and the idea is that the whole company and every group has one objective and three measurable key results, and if you achieve two of the three, you achieve your overall objective, and if you achieve all three, you’ve really killed it.

We put the whole company on that, so everyone knows their O.K.R.’s. And that is a good, simple organizing principle that keeps people focused on the three things that matter — not the 10.

Then I ask everybody to write down on Sunday night or Monday morning what are your three priorities for the week, and then on Friday see how you did against them. It’s the only way people can stay focused and not burn out. And if I look at your road map and you have 10 priorities for you and your team, you probably don’t know which of the three matter, and probably none of the 10 are right.

I can look at everyone’s piece of paper, and their road map shows every item you were going to do and your predicted results and actual results, and then the results are in red if you missed them, yellow if they’re close and green if you passed them. I think road maps are a great principle just for managing your life. It keeps everybody focused, and it lets me know what trains are on or off the tracks.

I really love this – it keeps things simple and achievable, breaking complex goals into very manageable tasks.  In the article, he also talks about making everyone the CEO of something, which is a nice way of saying, give people ownership of tasks – have them do stuff that matters.

Reblog this post [with Zemanta]

Lunch and Inspiration

January 8th, 2010
Jeffrey Dahmer
Image via Wikipedia

Just got back from lunch with a friend of mine named Zach Servideo. He introduced me to “The Black Sheep”, a restaurant located in an old Firehouse in Kendall Square which has phenomenal food. If you don’t know Zach, he’s a passionate PR professional who could befriend the most anti-social person in a room and turn them into an entrepreneur.  Needless to say, had Jeffrey Dahmer met Zach in the early 70′s, he would’ve started up a software company.

Zach is starting up a little side project called All White Kicks aimed at individuals interested in White Shoes. It’s a niche I would’ve never thought of, but with his passion, he can clearly make it work.

It also reminded me of my friend Alan who always has a few side projects going on. He’s experimenting with a few random AdSense pages such as My Reticulated Python and he’s also working on a niche site called The Curry Project, which aims to review every Indian restaurant in the world.

All of these side projects have inspired me, and I wanted to let you know about a new project I have called HapiMoney. Personal finance education is woefully inadequate and most people don’t know the first thing about where their money should go and in what amounts. I hope to shed some light on money management. Check it out and let me know if you have any ideas. Also, the name is awesome because Hapi is the Egyptian deification of the Nile flooding. This flooding helped water Egyptian crops and brought prosperity to the region.

These little projects also reminded me about one of the biggest mistakes that we ever made at WebNotes- we failed to follow the adage ” release early and release often”. The project was started in 2005 and wasn’t actually released to the public until 2008- 3 years of time which could’ve desperately used public feedback. But I’ll talk more about this in a future post.

Reblog this post [with Zemanta]

Moving On

December 20th, 2009
Office Space: Motion Picture Soundtrack album ...
Image via Wikipedia

This past week was a big week for me: I’ve officially left WebNotes and am searching for the next big thing in startup land! It was an amicable break up, so no feelings were hurt, and WebNotes is moving to the West Coast for a much needed restart.

In retrospect, it was a frighteningly fast sprint this past year and a half and I learned an amazing amount about entrepreneurship, software and marketing.  Now that I am no longer the head cheerleader for the firm, I will be trying to do a bit more teaching on this blog, instructing other wantrepreneurs (entrepreneur wannabe’s) how to be more efficient in their execution.  We made a ton of mistakes, and I hope you all can learn from them.

I wish the WebNotes guys the best of luck out in Cali, and I hope they are able to turn things around. And if you are a startup in the Boston area and are looking for some help in marketing, shoot me an email and we’ll grab a coffee to discuss.

Reblog this post [with Zemanta]