Kellan Elliott-McCrea
Head of Engineering, Adobe. On 1 show, 1 appearance. The Shows tab opens the full record on each.
executiveengineeroperatorinvestor@kellan ↗LinkedIn ↗kellanem.com ↗
He previously served as Chief Technology Officer at Etsy through its IPO, Vice President of Engineering at Dropbox, and Chief Architect at Flickr. Across the tech industry, he is widely recognized for pioneering continuous deployment practices, blameless post-mortems, and scaling engineering culture.
1shows
1appearances
33statements
2resolved
2supported
0contradicted
100%fully supported
Everything Kellan Elliott-McCrea said on any show that made the record, most notable first. Each card names its show and opens the statement there.
Elliott-McCrea: Slow engineering execution always stems from leadership's lack of clarity
“When I'm going and having these conversations with leaders, and this is, I think the standard conversation most people have is it starts with leadership. If we're moving too slow, it always does. We've always believed that we've been more clear. We've created …”
Elliott-McCrea: Dropbox's runaway early success created a flawed product development mindset
“Dropbox hit a home run basically out of the gate. And there was kind of an expectation that that's how you built products. And like people came from different places and very different experiences, but pretty deep in the culture was this idea that you build it…”
Elliott-McCrea: Google hires often struggle elsewhere because its internal systems don't replicate
“I think the canonical example of this is Google, by the way. I mean, I think that
Sort of in industry. Now we've kind of learned you hire people out of Google and they show up and they don't know how to operate because they've been such a determined high funct…”
Elliott-McCrea: Leaders should not automatically bring former colleagues into new organizations
“One of the things that people ask me is you look like you've worked with a bunch of great people. Like, do you just like bring them with you to every organization? And the answer is, of course not. Like every organization is different and partially I need the …”
Elliott-McCrea: Shielding engineering teams from company chaos causes them to misalign
“Actually, one of the early stereotypes about engineering managers in our industry is as the shit umbrella, you know, just gonna keep people from being distracted by all the crazy. And what that is, is those teams end up just drifting off. You know, you talk ab…”
Elliott-McCrea: Management quality matters more for scaling than code reviews or architecture
“You know, I really have come to believe that high quality management is one of the keys if you're going to scale your organizations. And so the degree to which I invest in that versus invest in architectural principles or code reviews or other things has grown…”
Elliott-McCrea: Data tools often validate employee existence rather than drive software
“I actually feel like a lot of the data products that are available today are really like targeting people's need to prove that their work is actually working or validate their existence within a team rather than actually driving the software to Development for…”
Elliott-McCrea: Engineering teams could shrink within five years
“I think that over the next 18 months to three years, I actually don't think we'll see substantially different changes, but over the next five years, I could see teams actually getting smaller again.”
Elliott-McCrea: Jira is built for control and predictability, not greatness
“Jira is not built for building greatness. You can use it that way. But fundamentally it's about someone who's trying to create a sense of control and a sense of predictability over it while at the same time actually asking to be surprised.”
Elliott-McCrea: OKRs have an undeserved bad reputation and work well
“I hate to say this, but at the most fundamental level, it looks a lot like OKRs, which have a bad rep, but are kind of great.”
Elliott-McCrea: Microservices are often proposed to avoid talking to coworkers
“I think that we see over and over again, technical solutions proposed around the idea of, I don't want to talk to my coworkers. I think microservices is like the canonical example of this, but we see it in all different ways.”
Elliott-McCrea: The tech industry faces a wave of disappointing internal platforms
“And one of the places where we see this really becoming a problem right now, and I think this is downstream of us all having so much success using Amazon, is that we really see the rise again of internal platforms and teams taking dependencies on, on these int…”
Elliott-McCrea: Company success does not always require high-quality engineering
“I think that one of the things we've realized is that there are actually multiple paths to success and multiple high quality ways to run a team. And that also that some companies
Path to success doesn't actually run through a high quality engineering.”
Elliott-McCrea: Pitting a team against others easily manufactures strong identity
“One of the easiest hacks for creating strong identity as a team is to put the team in a combative situation.”
Elliott-McCrea: Building businesses has gotten harder while software has gotten easier
“Building new businesses has gotten harder, even while software has gotten easier.”
Elliott-McCrea: Stack ranking and firing the bottom 10% damages company culture
“I'm not doing a sort of a stack rank and cutting the bottom 10% ever, because I think it has other problems with the culture that it creates.”
Elliott-McCrea: Managing software engineers during tech booms resembles managing volunteers
“Particularly when the industry is on an upswing, there is something similar to managing volunteers and managing engineers, even though you're paying the engineers a lot of money to do it.”
Elliott-McCrea: Capping Flickr's engineering team at 20 made it fragile
“Flickr was very famously a team of 20 people, and we never wanted to get larger than 20, which meant that once people started leaving, we didn't have a lot of resilience, and very quickly that organization got unhealthy.”
Elliott-McCrea: Team complexity scales geometrically with parallel work streams
“Fundamentally, the rule of thumb I use here is your team is your unit of concurrency. And so the number of work streams you want to be solving at the same time is how many teams you need. And so the more things you're trying to do at the same time, the more te…”
Elliott-McCrea: Modern software tools are higher level, not simpler
“We say the abstraction layer has gotten better, but in many ways we are using more sophisticated tools. They have not gotten simpler. They have merely gotten higher level and more productive, but they're not simpler to use.”
Elliott-McCrea: Engineering health should be measured at team level, not individual
“So your unit of measurement for health is at the team level versus the individual level, especially as you scale.”
Elliott-McCrea: Tech employee tenure averaged 18 months over the past decade
“For the last decade, you know, average tenure has been about 18 months in these kind of companies that we're talking about, which means it's very hard to actually build an experiment with culture in the way that we were for a while.”
Elliott-McCrea: 12 reports is the maximum span for effective management
“12 people is sort of the upward limit of where most people can manage effectively. You know, six to 12 with eight kind of being the sweet spot is just kind of how much most people can sort of juggle the amount of context you need for each individual in order t…”
Elliott-McCrea: Software problem timelines range from days to years based on clarity
“One of the things that's really different about software engineering than other types of engineering is the fungibility. Problems can take two days or they can take two years. And the fundamental difference is the excitement and clarity you have around the sol…”
One line per show, most statements first. The link opens Kellan's full record on that show: the calibration, argument clarity, speaking style and every statement made there.
| Show | Role there | Eps | Statements | Record | |
|---|---|---|---|---|---|
 IN DEPTHLEDGER | Head of Engineering, Adobe | 1 | 33 | 100% 2/2 | full record on In Depth → |