Brad's Books and Organizations

Books

Books

Organizations

Organizations

Hi, I’m Brad Feld, a managing director at the Foundry Group who lives in Boulder, Colorado. I invest in software and Internet companies around the US, run marathons and read a lot.

« swipe left for tags/categories

swipe right to go back »

Negative Maintenance

Comments (36)

I had a fun email exchange with an investor I’ve worked with for almost 20 years in response to something a CEO send out from a board we are both on. I said “fucking awesome.” He said “that’s an understatement.” I said “CEO is such a delight.” He said “CEO is negative maintenance.”

I loved this. So I’m going to use this post to think through the idea out loud and I’d love your feedback since it’s still a messy / blurry concept in my mind.

My hypothesis is that the opposite of high maintenance is not zero maintenance but rather it’s negative maintenance.

There are days that I’m high maintenance. Everyone is. But if you subscribe to my “give before you get”, or #givefirst, philosophy, you are constantly contributing more than you are consuming. I’ve talked about this often in the context of Startup Communities, but I haven’t really had the right words for this in the context of leadership, management, and employees in a fast growing company.

Suddenly I do. When I think about my role as an investor and board member, I’m often tangled up in complicated situations. I’ve often said that every day something new in my world gets fucked up somewhere. This used to be distressing to me, but after 20 years of it, if I don’t know what the new fucked up thing is by 4pm, I start to get curious about what it’s going to be.

We all know that creating companies from nothing is extremely difficult. The problems that arise come from all angles. Some are exogenous and some are directly under your control. Some are random and some are obvious. Some are compounded by other problems and mistakes, resulting in what my father taught me at a young age was the worst kind of mistake – one that was a mistake compounded on a mistake compounded on a mistake – which he called “a complicated mistake.”

Personally, when I find myself in a complicated mistake, I stop. I step back and pause and reflect. And then I try to figure out how I can change the dynamic into something positive, not continuing to build on my complicated mistake, but instead getting clarity on what the right thing is to do to get out of the ditch.

Negative maintenance people do this. I’ve seen, been involved in, and made some epic mistakes. The CEO I’m referring to above has a great company, but has also experienced some epic mistakes. How he handles them, works through them with his team, and his board, is exemplary. There is work involved by me and the other board members, but it’s not inappropriately emotional. It’s not high maintenance. It’s just work. Decisions have to be made and executed. And there are impacts from these decisions, which lead to more decisions. Ultimately this CEO is putting energy into the system as we work through the issue, which is where the negative maintenance (as opposed to high maintenance) behavior pattern arises.

I like this idea of negative maintenance people. I’m obviously trying to think it through out loud with this post, so weigh in and help me understand it better.

Brutal Honesty Delivered Kindly

Comments (32)

In yesterday’s post Mentors 4/18: Be Direct. Tell The Truth, However Hard, Joah Spearman left a very powerful comment about empathy.

“The older I get the more I realize that truth is something that is best coupled with empathy. Ultimately, you have to seek to understand before you can be understood and part of telling the truth is knowing that you’ll never know someone else’s truth until you hear it directly from them rather than assuming you know what someone has experienced or what’s best for them.”

This made me think of a deeply held belief that I hold with my partners at Foundry Group – brutal honesty delivered kindly.

When I invested in Moz, I thought a lot about TAGFEE, which is Moz’s code that reflects their core values.

Transparent
Authentic
Generous
Fun
Empathetic
Exceptional

I especially keyed in on Transparent, Authentic, and Empathetic as these three are core personal values of mine. However, these three ideas often come into conflict. It’s hard to be transparent and empathetic at the same time. Consider the situation where you fire a person. Legally, you likely have some constraints on what you say, limiting your transparency. You want to be empathetic to the person you fired, so this again limits your transparency (or, if you are transparent, you likely aren’t being very empathetic.) And then, at a meta-level, you will have some internal struggles with your authenticity around this situation.

The tension between the concepts is helpful as it makes you think harder about how you comport yourself is difficult, challenging, or complex situations.

The solution between me, Seth, Jason, and Ryan is to be brutally honest at all times but deliver feedback kindly.

While I’m sure we hold back on occasion, especially when one of us is unclear on what is going on, we subscribe to the notion of brutal honesty. We try hard to be fair witnesses in the style of my wife Amy, saying what we believe to be the truth. When it’s a hypothesis, we frame it as such. When it’s an assertion, we state that. When it’s something we feel strongly about, we preface it appropriately. And when it’s a fact that we are certain of, we are unambiguous in what we say.

No matter how difficult, sharp, upsetting, or confrontational something is, we always deliver the message kindly. We are not decedents of the Stepford Wives and we each have our own personalities, so “delivered kindly” means something different for each of us. But we never mean malice, harm, or disrespect. We are quick to own our opinions, especially when we are wrong. And when on the receiving end, we listen, and try to understand the other person’s truth, as well as our own, and then reconcile them.

If you sat in a meeting with us, you’d see no yelling. No pounding on the table. No grandstanding. No aggressive body language. No passive aggressive behavior. But you would hear a lot of brutal honesty, And you’ll hear it delivered kindly.

I Will Instead of We Should

Comments (15)

While driving down Highway 36 from Boulder to Denver for a FullContact board meeting, TA McCann told me a wonderful phrase that I’ve been carrying around with me for the past month or so.

“At RivalIQ, we’ve implemented ‘I Will’ instead of ‘We Should.’”

I’ve worked with TA since we invested in Gist in 2009. TA was a co-founder and the CEO. He’s been deeply involved in Techstars Seattle since inception. When RIM acquired Gist, he ran a big software team within RIM for two years. A year ago he co-founded RivalIQ. And last fall he joined the FullContact board. So he’s been around the block.

As part of working together, we’ve become very close friends. We ran the Madison Marathon together (my 17th). We’ve fought together in the trenches over some challenging issues. We’ve enjoyed each others’ friendship, advice, and guidance on some heavy personal issues.

TA embodies the concept of “I will instead of we should.” I’ve always known him to be willing to roll up his sleeves and just get something done. He’s quick to give feedback, challenge ideas, and ask questions, but he’s never afraid to do the work himself.

At Foundry Group, there are twelve of us. I like to believe we embody the “I will” spirit – if someone suggests that something is wrong or needs to be done, they do it. Sure – we pass things around and there’s some delegation, but there’s never a willingness to criticize or give feedback without a corresponding willingness to participate in doing the work.

It’s a small but powerful mental tweak that is similar to the I / We challenge I used to have. In this case it’s the inverse. By shifting to “we” instead of “I” when I talk about what Foundry Group accomplishes, our whole team gets the recognition for the work we’ve all contributed to. This is powerful externally. But internally, by saying “I will” instead of “We should” it puts the responsibility for getting it done on the person making the suggestion. Even if they only manage the work, they are still responsible for making sure it happens, instead of the non-specific and ephemeral “we.”

TA – thanks for the phrase. I continue to learn much from you.

Mix Strong Opinions With Big Open Ears

Comments (13)

Gluecon’s early bird pricing ends Friday, April 4th and I wanted to make sure you got the chance to register prior to the registration rates going up. When we started Gluecon with Eric Norlin six years ago, I don’t think any of us really had any idea about the true size of the wave of innovation that we were catching. Glue started out like a lot of tech conferences do, with a “business track” and a “technical track,” but we quickly realized what a mistake that was. Since then, Gluecon has transformed into a conference of what I assert is the  deepest technical content available around the topics of cloud computing, mobile, big data, APIs and DevOps. The agenda is shaping up to be something really special. Use “brad12″ to take 10% off of the early bird registration

One of the things I love best about my Foundry Group partners is that they each have strong opinions. Another thing I love about them is that they each have big open ears.

I know a lot of people who have strong opinions. I know a lot of other people who are excellent listeners. The venn diagram of the intersection of the two is uncomfortably small.

As I’ve written before, I love working with learning machines and silent killers. The best entrepreneurs are the ones who combine these traits.

I know a lot of people with strong opinions who think they are good listeners, but all you need to do is listen to a conversation between them and someone else to watch them talking all over the other person. Or asserting the same point over and over again, often using slightly different language, but not engaging in a process of trying to actually learn from the other person’s response. This is especially vexing to me when the person with strong opinions claims to have heard the other person (as in “I hear you, ok, that makes sense”) but then 24 hours later Mr. Strong Opinion is back on his original opinion with no explanation.

In contrast, I know a lot of strong listeners who won’t express an opinion. The VC archetype that I describe as Mr. Socrates is a classic example of this. I expect most entrepreneurs can give many examples of them being on the receiving end of a stream of questions without any expressed perspective, null hypothesis, or summary of reaction. I hate these types of board meeting discussions – where the VCs just keep asking questions but never actually suggesting anything. There’s not wrong with inquiry and I definitely have my moments of “I don’t get this – I need to ask more questions” but in the absence of a feedback loop in the discussion, it’s very tiresome to me.

Big open ears doesn’t mean that you just listen. It means you are a good listener. An active listener. One who incorporates what he is hearing into the conversation in real time. You are comfortable responding with a modification to an opinion or perspective as a result of new information. You are comfortable challenging, and being challenged, in the goal of getting to a good collaborate answer, rather than just absorbing information but then coming back later as though there was never any information shared.

I’ve always had strong opinions. I can be a loudmouth and occasionally end up in lecture mode where I’m just trying to hammer home my point. My anecdotes and stories often run longer than they should (I blame my father for teaching me this particular “skill.”) But I always try to listen, am always willing to change my opinion based on new data, or explain my position from a different perspective after assimilating new data. When I realize I’m bloviating, I often call myself publicly on it in an effort to shift to listening mode. And I always try to learn from every interaction I have, no matter how satisfying or unenjoyable it is.

Do you have strong opinions AND big open ears?

The Duo

Comments (8)

I’ve been thinking about the concept of “the duo” a lot recently.

Many of the companies I’m involved in have either two co-founders or two partners who partner up early in the life of the business. Examples of founding partners including Andrei and Peter (Kato.im), Keith and Jeff (BigDoor), James and Eric (Fitbit), and Matthew and Cashman (Yesware). Of course there are many other famous founding duos like Steve and Steve (Apple), Jerry and Dave (Yahoo!), Larry and Sergey (Google), and Bill and Paul (Microsoft). My first company (Feld Technologies) had a duo (me and Dave) and the company that bought Feld Technologies did also – Jerry and Len (AmeriData).

But many of the companies I’m involved in have duos that develop over time. Sarah and Rand (Moz). Bre and Jenny (MakerBot). Matt and George (Return Path). David and David (Techstars).

Now, these duos are not the leadership team. But there is a special magic relationship between the duo. I like to think about it like the final fight scene from Mr. and Mrs. Smith where Brad and Angelina are back to back, spinning around in circles, doing damage to the enemy.

This is not just “I’ve got your back, you’ve got my back.” It’s “we are in this together. All in. For keeps.”

It’s just like my relationship with Amy. We are both all in. It’s so powerful – in good times and in bad times.

Build something great with me