What Doomed MakerBot? The Osborne Effect

2015-04-18T00:00:00-05:00

What Doomed MakerBot? The Osborne Effect

On April 17, MakerBot laid off 20% of its staff. That's a big deal to me as I've been wondering what happened to the MakerBot I used to admire. Years ago, I looked up to the MakerBot team as a role model of how to run an open hardware company. Bre Pettis, MakerBot co-founder and former CEO, had given many talks and had written many times about the virtues of open source and how it was critical to their early success. Here's what Bre said about open source in 2011:

Make: Does funding change the commitment to open source hardware?
Bre: The funding doesn’t change our commitment to being open source. Why would we change a winning strategy? Being open is the future of manufacturing, and we’re just at the beginning of the age of sharing. In the future, people will remember businesses that refused to share with their customers and wonder how they could be so backwards.
Our commitment to open source stems from our passion for sharing. We know that if we share with our users and the world, there is a natural positive effect.

So in 2012, when Bre announced that MakerBot was closing its future designs, I wasn't satisfied with his explanation. His words rang hollow and insincere. It was also sadly ironic he made this announcement to a room of true believers at the Open Hardware Summit. In Bre's words:

"Some of the shifts we’ve just made, that’ve made some people grumpy. We are not sharing the design files for the body of the Replicator 2. That’s because it’s powder coated steel, and unless you have, like, an open source steel bender, you’re not going to be able to do this, it’s not something you can do, at home."

Really, that's it? Open source ends the moment it involves bending metal and powder coat paint? Why not fund the creation of that open source steel bender? What's really going on here?

A few days before his Open Hardware Summit talk, Bre tried to lay the blame on cheap Chinese clones, like the Tangibot. Others, and notably fellow MakerBot co-founder, Zach Smith, remained skeptical, saying "I look at a move to closed source as the ultimate betrayal." For years, many continued to doubt Bre's statements.

Another opportunity for Bre to discuss the issue appeared in the Netflix documentary, Print the Legend, released in 2014. Here's what Bre said about open source in the movie:

"You can't live in the fantasy world and have a business, too, sometimes."

Gee, thanks, Bre. Again, why do you think that's true? How did you come to that conclusion? What do you know that those of us still in the "fantasy world" don't know?

I would like to know because, someday, I hope to start a hardware company based on open source principles, just like MakerBot did. It would be the second time I've founded a company based on an open source project I started. My hardware product is a robot, called Tapster, which software developers can use to test mobile apps on devices like iOS and Android phones and tablets. Tapster is completely open source hardware and most of its parts are 3D printable. For the past three years, through a site called Tindie, I've sold my robots to major mobile phone manufacturers, car manufacturers, and software companies around the world. As the project grows, I'm determined to remain true to open source ideals. Yet, I wonder, thanks to MakerBot, are those ideals fundamentally incompatible with making a profit?

Just when I thought Bre's reasons would forever remain a mystery, I found this recent interview with Bre. Buried in there, I believe we finally get the real reason MakerBot went closed source:

"For a while, we tried to have this super utopian business model that was probably more befitting of nonprofits, where we just shared absolutely everything we were working on." One of those things was a rough sketch for a second 3D printer model. The good news? Word spread like wildfire among MakerBot fans who were immediately sold. The bad news? Everyone stopped buying the first generation printer to wait for the latest and greatest — which was still a year away.

"We got through it somehow, but we definitely shot ourselves in the foot that time," Pettis says. "And you can only shoot yourself in the foot so many times before you can't walk anymore."

So where does he land on sharing today? Don't hesitate to reveal the inner-workings of your decision-making process if it would strengthen your dialogue with customers. When it comes to business plans and unreleased products, however, think (and then think again) about potential fallout. Once a story is out in the wild, there's no getting it back.

Aha, that's it! MakerBot fell victim to the Osborne effect, where talking openly about future products hurt the sale of their current products. Sales dropped, so they got scared and went closed. That sounds like a way more honest and real answer than the non-existence of an open source steel bender.

What's harder to link, however, is the connection between MakerBot's Osborne moment, and yesterday's news of layoffs. But that won't stop people like me from speculating! When MakerBot closed their designs, they burned a bridge with some of their loudest supporters, their early adopters. Those early adopters felt burned, and returned the favor by not recommending MakerBot to their friends and families anymore. Did the bad publicity from the decision to go closed source have a larger impact on the company than the Osborne effect of being too open? We'll never know for sure. Or perhaps, we'll just have to wait a few more years until they're more open about it.

Discuss this on Hacker News or heckle me on Twitter.

What's in a Name

2014-06-24T00:00:00-05:00

What's in a Name

When he got to me, I extended my hand and said the customary "Nice to meet you, Mr. President."

I added, "My name is Jason, but my nickname is 'Hugs'."

He FROZE.

It was only for a moment, but felt like a minute. "Oh no," I thought to myself. What have I done?

Then he smiled, and said, "Come on, you get a hug!"

Everyone else was like "Wait, you got a hug!?"

Later, someone came up with a theory on why he froze: The president was just glad my nickname wasn't "French kiss".

Epilogue

I've told this story a few times, and I now realize I have to clarify something: He hugged me. I went in for the handshake, but he escalated. No begging for a hug here!

Ironically, I’m more of a fist bump guy. But he'll never know.

24 June 2014

HealthCare.gov 2.0

2014-06-23T00:00:00-05:00

HealthCare.gov 2.0

Last fall, I was honored to be on the "tech surge" team of outsiders that helped fix HealthCare.gov. I was on-site in the D.C. area for almost all of November and December, helping mostly with tasks related to test automation.

As of last week, I've rejoined the HealthCare.gov effort. I'm taking another leave of absence from Sauce Labs to help Ad Hoc and the Marketplace 2.0 team.

Long term, government needs to get better at software development, including test automation. For now, the best way to fight that fight is by example. If the Marketplace 2.0 team can help the government avoid last year's drama when open enrollment begins again in November, then we'll have a good story to share with other departments and agencies. But if we get a repeat of last year, then it'll be a lot harder to convince government officials to change their ways.

So... no pressure...

23 June 2014

Jason Huggins

What Doomed MakerBot? The Osborne Effect

What Doomed MakerBot? The Osborne Effect

What's in a Name

What's in a Name

Epilogue

HealthCare.gov 2.0

HealthCare.gov 2.0