Posts in DeveloperTown
Competition

The following is an excerpt from an email I sent to DeveloperTown in April 2016. 

I love competition. Where none exists in my life, I'll go out of my way to create it. It's a big motivator for me. But it's not my only motivator. I'm also very motivated by fraternity, and by wanting to help others.

Competition in business is an interesting thing. In his book The Hard Thing About Hard Things author Ben Horowitz talks about "wartime." From Horowitz:

"In wartime, a company is fending off an imminent existential threat. Such a threat can come from a wide range of sources including competition, dramatic macro economic change, market change, supply chain change, and so forth."

By that definition, we (DeveloperTown) are not at war. While we have competition, none of it is an "imminent existential threat." When you think of that kind of competition, you typically call to mind epic winner-takes-all battles like Explorer vs. Netscape, Apple vs. Microsoft/IBM, and MySpace vs. Facebook.

This is a good thing. I don't want to have to fight another consulting company "to the death" to have to remain in business. While I'm sure we would rise to the challenge, it's not really the kind of fight one should go looking for.

Instead, we are lucky enough to be in a market and industry where we can partner freely with other firms with very little fear of a significant loss of market share. Right now - and for the foreseeable future - there is too much demand, and not enough qualified people to do the work. Because we are in professional services - and not a product that could scale to take the entire market - we aren't in danger of a winner-take-all battle.

That said, I still like competition. I like winning. I like what lessons I often learn when I lose.

In the early days, we competed against Expected Behavior. We don't really compete against them any longer. They've largely pivoted into products. But for about a year, you could find a whiteboard (I think it was mine) with a short tally of deals we won vs. deals they won. This was of course at a time when our teams also socialized together - game nights, team events, etc. It was the model of friendly competition. We competed, but we weren't jerks about it. So long as the client chose one of our two firms, we were happy with the client's choice. (We were most happy when they chose us.)

Today, we partner with: NOI Strategies, Anchor Point, InGen Technologies, Mavenly, BMI, MilesHerndon, Fretless, Foxio, and a bunch of independents. And we'd happily partner with more firms. But we find that most larger firms are hesitant to want to partner. They'd rather win all the work. I'm sure we would rather have all the work too... but that doesn't mean there's not good reasons to partner with someone else from time to time.

Competition is also on my mind because of this week's Verge event. It's been a few months since I've attended a Verge event. It was a great event - a couple of solid pitches, one questionable pitch, and a great fireside chat. But something was different. Matt has started to be much more vocal about his sponsors. He now actively promotes them in between pitches. I don't know when he started doing this, but I noticed it for the first time this week.

This was difficult for me. The first two sponsors he promoted were 1150 and Innovate Map. He said very nice things about them. He said that 1150 is the best place in Indy to go for an MVP. And he said that Innovate Map was the best firm in town to help you define your product and plan it's go-to-market strategy.

I know Matt was just promoting a sponsor. I know Matt recommends us all the time. I knew Matt would be promoting us later that evening. But when I heard those promotions, it hurt. I want us to have that work. I want us to be recognized as the best in this market for those things. I want to win.

It's an unrealistic expectation. 1150 is likely the right choice for some people. Innovate Map is likely the right choice for others. We can't - and shouldn't - win all the work. Intellectually, I understand that. But emotionally, I still want to win.

I think this is a good thing (for me), because it causes me to do a handful of things:

  • It causes me to review what our competition is actually doing. What services does 1150 offer now? How do they position it? What's Studio Science up to these days? Has Fretless grown? Has High Alpha actually done anything yet? Is Element Three doing more app dev work these days? Has LEAP officially opened their Indianapolis office yet? When I reflect on the market, it kicks off a series of questions related to our competition. I'm not good at digesting what our competitors are doing on a daily basis. I tend to check in on their activities in spurts.

  • It causes me to reflect on our position in the market. Are we still really the firm I picture in my head, or have we moved to a new spot in the market? Are we actually the best place to get an MVP, or do I just want us to be the best place? Are all of our competitors offering something we aren't offering? Should we be offering that thing? What common about the customers that choose us, instead of those that choose our competition?

  • It motivates me to take action. All that reflection leads me to identify things I want to change. Maybe it's how we position ourselves. Maybe I think we need to change our offering to the market. Maybe I need to get over it, and extend an olive branch to someone and try to find a way to partner with them instead of trying to find a way to "beat" them.

(To be clear, Matt did eventually say very nice things about DeveloperTown. And there have been previous Verge events where it has been an almost palpable DeveloperTown-love-fest.)

​A bit more from Horowitz:

In peacetime, leaders must maximize and broaden the current opportunity. As a result, peacetime leaders employ techniques to encourage broad-based creativity and contribution across a diverse set of possible objectives. In wartime, by contrast, the company typically has a single bullet in the chamber and must, at all costs, hit the target. The company’s survival in wartime depends upon strict adherence and alignment to the mission.

[...]

A classic peacetime mission is Google’s effort to make the Internet faster. Google’s position in the search market is so dominant that they determined that anything that makes the Internet faster accrues to their benefit as it enables users to do more searches. As the clear market leader, they focus more on expanding the market than dealing with their search competitors. In contrast, a classic wartime mission was Andy Grove’s drive to get out of the memory business in the mid 1980s due to an irrepressible threat from the Japanese semiconductor companies. In this mission, the competitive threat—which could have bankrupted the company—was so great that Intel had to exit its core business, which employed 80% of its staff.

DeveloperTown is a market leader in Indianapolis, and we're at peace. (Despite what my ego says.) That means we don't need a "single bullet" that needs to hit the target at all costs. We won't be focused on "one thing" this year - or likely in the next couple of years. Instead, our strategy is to explore a number of initiatives. We want to leverage the different passions and interests of our team. Some of those include:

  • Purposeful marketing and PR efforts - something we've done vary rarely

  • An attempt to solidify some of our thought leadership around innovation and how we build and launch products

  • A new offerings to early stage startups - where we think a new way to structure engagements can dramatically reduce risk for those starts

  • Exploring selling and expanding into new "local" markets outside of Indiana

All of those are a reflection of us trying to expand our markets - or expanding our reach within a market. They are not dramatic shifts to new businesses or direct responses to competitive threats. As we continue to solidify what some of these efforts look like, we'll start to further engage the team in defining them and rolling them out.

Have a good weekend.

Mike

 

Bees, Experience, and Craftsmanship

The following is an excerpt from an email I sent to DeveloperTown in March 2016. 

This week I purchased bees for the farm. It's a bit scary for me. But Patrick decided that bees would be this year's farm experiment. (That's the last time I let him choose.)

You know the security questions for username and password verification on websites? The ones where they ask, "What's your greatest fear?" Guess what my answer to that is? Bees.

Gulp.

Like with any new animal experiment, I have to immediately read four books on the topic before I feel like I'm even remotely prepared. Bees are no exception. I've already read most of Beekeeping for Dummies and a few months ago I started listening to a beekeeping podcast.

Yup... There are beekeeping podcasts. God bless the internets.

In the Beekeeping for Dummies book, the author makes an interesting point around getting started. The book covers everything you'd ever want to know: bee biology, the hive, basic tools, lifecycle, selling product, etc. Some of it's actually awesome. Did you know that bees breath out of a bunch of little holes on the sides of their bodies?

In the "Getting Started" section, the author mentions that, for most beginners, no matter how closely you follow the "instructions" for getting started with bees, it's likely that for the first few years you're going to fail. He points out ten or so small nuance mistakes you will likely make, even though you're "taking all the right steps" that will likely result in the death of your hive. And he then points out that those are simply ten out of hundreds of those small mistakes.

Experience.

This is experience. It's the difference between knowing the "steps" to doing something, and then getting the actual desired results from following those steps. It's the same with many nuanced tasks (think baking, playing music, or fishing). You might know exactly what to do, but that doesn't mean it will work.

The crappy thing about experience is that there's only one way to gain it. You have to do that thing. You have to plan to make mistakes. To fail. And to learn and grow. That means, if you want to raise bees, you have to be ready to kill a lot of bees through trial and error. (This process sucks for the bees. But this email isn't really about them.)

Think about what differentiates DeveloperTown from our competitors. Many consulting firms do work with startups. Many many more do work with large companies trying to launch new products. All consulting companies sell their "processes" and their "people." And we're no exception: "Hire DeveloperTown, we have a killer process refined over a 100+ projects, and we have a team of people who specialize in the art of the start."

That's not much different than the pitch other consulting companies make.

Craftsmanship.

In 2008 Richard Sennett published a book entitled “The Craftsman." In that book he lays out his theory for what sets the craftsman apart from the "average worker." For Sennett, craftsmen "complete their work with abandon and always want to do well for their own sake.” For him, the craftsman stands for “the special human capability for committed conduct”.

The fundamental idea for Sennett is that expertise (aka experience) - not accomplishment - is what differentiates the craftsman from the "average worker." Many people accomplish tasks and projects, but not everyone gains purposeful experience in doing so. It's the craftsman who thinks about growth through experience as a "way of life."

Back to bees... If you want killer honey, I've read that you need to move your hive throughout the summer. You need to expose the bees to different types of flowers, trees, and conditions at different times of the year. If you want "okay" honey, you can just get bees and figure out how to not kill them. But if you want truly great honey, then the creation of truly great honey has to become a "way of life."

You have to beecome a craftsman.

What will truly differentiate DeveloperTown in the long run? Are we here to knock out client projects, and maybe gain some experience for our resumes? Or are we "completing our work with abandon" and being purposeful in the way that we learn so we can get better and better at the "thing" that we're specialized in? Do we really view our role in "the start" as a special thing?

We aren't always craftsman all the time. I'm trying to learn to be a better leader. I have a lot to learn, and I'm trying to take a craftsman's approach with my learning. But I'm not trying to be a craftsman in all aspects of my life - with other tasks. I don't think that's possible.

In most ways, my experience is average. In some ways, my experience is special. When it's purposeful, it's not just "accomplishment", it's growing me to become better at my core.

I think we are craftsmen at the start. And I believe we can (and will) get better at it. But to do that, we need to become purposeful in our learning. That means we need to be purposeful as individuals, and as a team.

In the coming months, as we look to better define our processes for innovation and how we build products, an underlying part of that process should include defining how we learn and adapt. I think this type of learning is easy to do as individuals, but it's much more difficult to do as an organization. And it's really hard to make it a "way of life."

But I'm looking forward to the challenge...

Have a great weekend,

Mike