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!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…