Skip to main content

The store that sells only one thing.

3 min read
: Tech consultants who define themselves by a single language or framework are like a store that only sells one product. Customers come in with problems, not solutions.

Imagine a store. This store sells only one product. Regardless of what you come in for, regardless of what question you ask, their recommendation is always the same: you should buy the only product they sell.

Sadly, this is all-to-often the face of professional services in the technology industry. We have “Drupal shops” and “WordPress shops” and “Rails shops”, but no “problem solving shops”. Yet, we know that people come to technology consultants with problems, not solutions. Imagine, for example, if Deloitte, or any other of the big four consulting firms for that matter, was a “firing shop”. That every time you came to them with a problem, they would always suggest that you fire people. Or maybe they’re a “business analytics shop”. Doesn’t matter. Regardless of what problem you bring them, the solution’s always the same: “Do [the only thing we know].” Hard to imagine they’d stay in business long, huh?

But that’s exactly what we do in technology. Traditional software engineers define themselves as a “PHP Developer” or a “Rails Developer” or a “Java Developer”. The solution defines who they are. The past defines the future. That’d be like an architect that only builds round buildings or a handyman that shows up for a job with only a hammer in his toolbox. No matter what you ask for, the answer’s always going to be the same. “[That thing I did yesterday].”

But technology problems come in many yet unseen shapes and sizes, and often times the best solution isn’t the same one you used on the last problem, or better yet, hasn’t even been invented yet. Hackers, on the other hand, at least from my experience, often define themselves as a “developer” who has used a given language. There’s already the possibility there of learning another if the job calls for it. It’s a sense of solving the problems at all costs. It’s a sense of avoiding self vendor lock-in. It’s a passion for technology, not a technology.

When a potential customer comes to a technology shop, they’re not shopping for mere muscle. They’re not hiring unskilled labor. They’re shopping for experts. They’re shopping for people with a better knowledge of the space than they have. They’re shopping for a solution. Sure, a firm can specialize in something, or be known for a given skill. Nordstrom is known for its service. Apple’s known for its design, but Nordstrom doesn’t just sell blue shirts, Apple doesn’t just sell desktop computers, and neither should you.

Originally published February 27, 2013 View revision history
Share

More to explore

How not to prioritize a feature

7 min read

The hardest part of software development is not coming up with features to build, but instead, deciding what features will have the biggest impact.

Twelve things a product manager does

10 min read

What does a product manager actually do all day? After six months of note-taking, here are 12 responsibilities from user advocacy to strategic thinking.

Go near, go far, meet in the middle

5 min read

A three-phase approach for product managers joining established teams: tackle known wins, build a shared vision, then discover how to get there.

Why open source

17 min read

Open source isn't a fad. Here are twenty-five economic, moral, and personal reasons your organization should embrace it.

Removing a feature is a feature

8 min read

Features aren't free. Every time you remove one that doesn't serve your core use case, you're adding an implicit feature that does.

Ben Balter

I'm Ben Balter — I write here about engineering leadership, open source, and showing your work. I was the Director of Hubber Enablement at GitHub, where I helped thousands of GitHubbers do their best remote work. Before this role: Chief of Staff for Security, enterprise PM, and GitHub's first Government Evangelist. Before GitHub: attorney, Presidential Innovation Fellow, and member of the White House's first agile development team. More about the author →

Follow along: Bluesky LinkedIn

This page is open source Help improve this article on GitHub