Skip to main content

Who are you selling yourself to?

I just had a quick exchange over twitter in regards to Redbeacon being bought out by Home Depot.  First of all I want to congratulate Yaron, Aaron and the rest on starting a great company that got great traction.  Secondly why the hell did you sell to Home Depot?

I understand that a lot of folks in this world right now do startups and want to cash out.  If that’s why you are starting a venture – great!  You are basically running an R&D department for a big company, but if you are really passionate about your space selling to a company that sells 2x4s is a sure way to get marginalized and become irrelevant.

I have spent time in companies big and small.  I have created new features, new marketplaces, worked with partners and developed products.  In order to become a great company sales, marketing, development and executive sponsorship need to be in sync.

I can understand that a small product can be absorbed into a bigger offering and accelerate because of that acquisition, but when a company’s missions are so different it’s hard to imagine how the executive sponsorship, marketing and sales are going to rally behind the new lines.

Even when the company’s mission is aligned with your product’s mission it’s still hard to get the right support.  I’ve developed several projects that ended up going nowhere because the company was not aligned behind them.  Engineers put everything together and then… nothing.  It’s demoralizing and you can’t get folks to work hard on the next revision.

I think in a pinch Home Depot has to compete with Lowe’s on the best home improvement hardware and materials, not a web 2.0 solution for locating contractors.  My guess is that pouring money to market and evolve Redbeacon is going to be less of a priority than the core business.  Let’s hope I am incorrect.
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…