Why is software so bad?
Akimbo: A Podcast from Seth Godin
0:00
0:00

Full episode transcript -

0:0

40 years ago, I drove a brown Fiat Strada, perhaps one of the 10 worst cars ever made. It went 0 to 60 in about 19 seconds. It got about 20 miles to the gallon. The back seat was remarkably uncomfortable. It handled poorly, and it was really ugly today for about the same number of inflation adjusted dollars. I drive a Toyota Prius plug in hybrid. It gets, Ah, 199 miles to the gallon. It goes 0 to 60 just as fast as I needed to. It's super safe, and the backseat is quite comfortable. Hey, it's F,

and this is a Kimbo way back in a second after this message from our sponsor. I don't really want to talk about cars today. I want to talk about software, and I want to talk about why software is so bad. I developed my first computer game as a hobby in 1976 when I was in high school, and I was super fortunate in the early eighties to do it professionally. In those days, making games for the Commodore 64 our major limitation was hardware. This is what the music sounded like. The text was so clunky, it was almost unreadable. The graphics were nothing to write home about. We were busy pioneering how software might work At the time I was beta testing the original Mac and the Mac was a revelation on that. Mac, I had a word processor soon after that. A spreadsheet.

Today, 40 years later, I have a word processor that does almost exactly what that word processor did 40 years ago. I have a spreadsheet, Google sheets that does less then the spreadsheets I used to pay for. Sure, it's free. Sure, it's connected and can have multiple users, which makes it even more useful. But in terms of software development, if we leave aside the network effects, most of the things that I and you do with software are not dramatically better. Then they were soon after the Mac came out. Why is that? What happened to this industry?

It is no longer driven by hardware. The hardware is now as fast as we need it to be. The screens are as sharp as we are able to discern, and the colors, unless you're a sea slug, are infinite. So what all this means is that software the architecture of software isn't what it could be. I want to share a few reasons why I think this is the 1st 1 is the buying cycle. Cars have made a lot of forward motion, even though they're largely hardware dependent? Well, why is that? First, there's a buying cycle. Every 3456 years, we take a deep breath and we start over.

The operating system of the car hasn't changed in almost 100 years. If you know how to drive one car, you know how to drive almost every car. But when we start over, we can switch brands. We can go from Company A two Company B, and we're about to spend $50,000.30,000 dollars, $70,000 for the privilege of doing that. Which means that the car companies are under a lot of pressure to create something that users think is better. That's not true with word processors or spreadsheets or video editing software. We are stuck with the operating system with the method with the U I with the file format that we're used to. Number two car companies have dealers and dealers talk to consumers face to face. Dealers live and die every day. Dealers see that people are walking off the lot, and they're happy to scream directly at the people at the car companies who have no choice but to listen to them. That's not true for software.

Software isn't sold for the nearly the same price to a consumer, and it's usually sold directly without a middleman. Number two. As we discovered about 20 years ago, the network effect is actually the killer. APP. Software exists primarily today to connect us to other people that the way Microsoft ended up destroying word Perfect was by showing up with file formats that could be shared one person to the other. It wasn't worth it. Once someone in your office was using word for you to insist that it had a work with word perfect share a bowl file formats meant that it went in one direction. Google gives its software away, but we'd probably pay for because the magic of the network effect is so overwhelmingly powerful. We would forgive the fact that you can't do nice typography and other features in Google docks. We would get over the fact that Google Sheets isn't as fast or as reliable as Excel at its best because the network effect multiple users using thing overwhelms everything else. As a result, the biggest brains, the smartest people the hardest driving focus at every software company tends to be about.

How do we get people to share this? Not how do we architect it with care so that the experience of using it on your own is delightful. Number three, which might be the biggest one, is that software is complicated. It's complicated for the user. When I think of how many instructions I need to give somebody to be ableto learn to drive. A new car is probably three minutes. Here's one button. Here's the lighter. Here's how you turn on the cruise control and don't forget about this. Off you go. You can walk into a rental car agency, get a car you've never driven and drive it off the lot. Software isn't anything like that. That the number of options,

because options air super easy to add, keeps increasing. One person wants to, I don't know, composite reverse type in these colors with an Alfa Channel, and suddenly that's one of the features. As a result, the architecture of software is significantly more complex because the architect doesn't know what the user wants to do. And there is no convention that has been accepted for turning off features so that you can have the version that you want and have it work the way you want to use it. The next idea is that culturally, we stopped giving prizes for craftsmanship that when the early versions of Keynote came out, people moved to it away from Power Point because it was well crafted. But that was more than 10 versions ago. Since then, there hasn't been a lot of discussion about what it means to be good at crafting how to create presentation software. I think you and I could sit down and come up with 20 ways to make it significantly better that one.

A new company like Crazy comes along. What we noticed are a couple gimmicky moves. Not that it is perfectly crafted the way perhaps a Porsche is a better crafted car from the user car experience born of you, Not that you asked. But if someone has given more than 1000 presentations using keynote, here are some of the things great presentation software would do to make my job easier and to make the experience of consuming the presentation better. Number one. How come there isn't a timer built in that shows me compared to what I expect? Where I am through my presentation, Show me with colored lights that I'm behind or ahead. How come there isn't a way to group up subsections? Have a presentation so I could sub them in. Turn them on, turn them off easily, not with some sort of clunky hierarchy. Number three.

Why can't I instantly glance through all of the material I've used in the past to find which subsets air available? Which ones I want to add? It goes on and on. None of these features have been ad instead, What I've got is now the ability to change the outline on a font, which no one has any business doing. That's not what it's for, but nobody seems to be in charge of making keynote more elegant and useful. Instead, it's sort of a random collection of ways to get more people to share it and use it together. It's not becoming more powerful or more beautiful. It's simply becoming more clunky. The same thing is true with almost all the software I use. Apple, which used to lead the way in figuring out how to give us power and leverage, now dumbs things down because there are a luxury brand,

not a group of people trying to craft tools for folks who are trying to change the culture and then back to this idea. That software is complicated. We've been trained to put up with it. So a specific example. About four years ago, some versions of the Mac laptop began to lose connection with WiFi networks. Sort of randomly. No one's exactly sure why. And you confined posts online from 15 16 78,018 with people complaining about the same bug with solutions that verge on witchcraft. Delete this. Do that stand on one foot over and over again for years and years. Try to imagine a car that didn't work at many gas stations on a regular basis, and no one knew why the filler cap wouldn't open at some places under some circumstances. Try to imagine that this went on for year after year after year of the car being sold. I think it's pretty easy to believe that that car would be recalled, that that brand would plummet in value,

that our standards for what we're looking for from our $40,000 car are really different from what we're looking for from the software that we make a living using every single day. Now, users are complicity because as software companies stopped caring about the quality of experience, users started stealing the software because the network effect is powerful because incrementally, a second copy of a piece of software in the world doesn't cost the company money the way it would cost Ford Motor money if you went to a dealer and drove a car off the lot without paying for it. Conceptually, digital goods have always had this marginal cost problem. It doesn't feel as wrong to steal software as it does to steal a car. None of this would matter, except that software drives the culture. When they came up with new ways to do editing new ways to do special effects, The movies we watched began to change the Terminator. That guy with silver skin happened because someone made software that would enable it toe happen. That changed our understanding of how the future might look. That changed the kind of cars that got made that changed our expectations of what tomorrow would look like. Software changes not just the way our movies look.

It changes the way that we tell a story. It changes the way we consume a story. It changes our attention span that the network effect at all costs means that we've got Clickbait. It means that people are hunting around for hours every day on their smartphones, a device that didn't even exist when I sat down with that first Mac that was on my desk. Our attention span has been shifted because software engineers are in a hurry. And this lack of care about architecture and user delight, combined with the overwhelming effect that networks have means that we are victims of a cycle that has been driven by 100 or 1000 cutting edge software engineers who are making decisions making decisions about whether to make something more beautiful or more profitable, making decisions about what tools we're going to have or not have about how long we should spend on something before we get to the next thing we began with software being our tool, a tool to help us do our work. But over time, we have become software's tool that we exist to enable software to reach its goals. And its goals are to turn us into subscribers networked, paying subscribers who keep making more stuff that enables the network to thrive. It is entirely possible that hardware isn't going to get much better that backward. I was making games for the Commodore 64.

I saw ah, hard drive burst into flames because our software was making it work too hard. And yet, just last week, Google updated Chrome, which caused the editing stations of hundreds of companies in California that we're making cutting edge commercials and movies to stop working on their max. Totally stopped working, unable to reboot, to do anything that's 40 years later. Software is a mess. Software is complicated, software is driven by the network effect, and we are the victims of it. If we stand up, speak up and argue that this thing that we're spending our entire day using ought to be better. If we establish standards,

awards heroes, maybe we'll find another. Andy Hertzfeld maybe we'll find another Susan Cain. Maybe we will find another Siri's of architects and designers who will insist it's software can be beautiful, that it could be powerful that it can help people express the ideas they want to express, as opposed to being victims of a commercial system that doesn't have our best interests at heart. That's my rant. Thanks for listening. We'll see you next time. Thanks for listening. We'll be back in a second with three questions from last time. But first, here's a message from our sponsor.

16:26

It's It's It's mighty and accept. My name's Kyle reading. Seth, this is Steven out in Madison, Wisconsin. I said Alicia from Charleston here. Hi, Caitlin. Warm greetings from curious. Oh, hey, Seth. My name is Nick Ryan from Pittsburgh, Pennsylvania. Hey, sent Mrs Rex. Hi,

this is Hi, this is Roberta Perry. My question is on. That completes my question. E.

16:52

I really do love hearing from you. And it's OK if you want to ask a question that isn't about this week's

16:59

episode. The question that isn't related to any specific episode, just something that I was going through. My question is more of a general question rather than the topical of this

17:10

podcast To ask your question, Just visit a kimbo dot link. That's a k i m b o dot l i n k and press the appropriate button.

17:20

Hello, Seth. Ever so very year from Toronto, Canada. You keep nation here and there throughout your podcast. That's we are in an open marketplace moment in time. But maybe this will change in the future when we have an open market place, as we do now. But maybe not for long. It seems that you are painting the future that we are inviting the gatekeepers back in the building. This is warning, And what are you referring to? Is that about net neutrality? What is it? Are inviting the gatekeepers back in the building?

17:56

Something dramatic has happened in the last 15 or 20 years. And it's this 100 years of gatekeepers, right? 500 years of gatekeepers are being replaced by systems that air dramatically more open. If you wanted a business profile written about your company in 1974 while you could use Business Week, Forbes or fortune and that was pretty much it. Now you can write your own now you could be featured on more than 510,000 1,000,000 websites that could talk about you in the 19 eighties. If you wanted to be on TV, there were three, maybe five people who could put you on TV. Now you can put yourself on TV one medium after another sound video text, all of it wide open. But my instinct is that that can't last. It can't last cause over time people seek to consolidate toe lock in to create monopolies and oligopolies. And we're seeing it, for example, in what Netflix is trying to do in the business of television.

Of course, Apple and Amazon are racing after them as hard as they can. But this idea that there would be an open place where someone could make a thing and get paid to make it while already we're getting boxed in. We're getting boxed in as podcasters consolidate as people in the movie business consolidate, because that is where the stock market wants them to go because they want to extract the maximum amount of revenue. So my argument begins with that, and then proceeds to the idea that there's only a finite number of people of voices that a listener can follow. That permission is a self limiting function. Once you've got your problem mostly solved, you stop giving permission to new voices to new options. And so we have this wide open area, this land that's being carved up. And I think if you seek 1000 true fans, if you seek to change the culture, waiting is not your friend. Diving into it now makes a lot more sense.

20:21

Hey, Seth, this is Neil from Portland, Oregon. I am a huge a Kimbo fan and anxiously wait each new episode each week. I feel like I'm a living, breathing embodiment of one of your core messages, which is, if you do good work, people will follow it in the old, share it with others. I find myself talking with friends, family and colleagues about your episodes and share each podcast episode with them. Kimber is a really interesting example. Which brings up my question is how do you create content that is more share a bowl? I was talking with someone about slack in their business and wanted to share in a Kimbo episode with them, but found it very hard to search for that episode so that I could send it to him. Thanks again for all the work that you do looking forward to the next episode.

21:7

Yeah, share ability is one of the factors in how ideas spread or how viruses spread. We know, for example, that the measles has an are not of up to 18 1 person with the measles can infect up to 18 others. That's why it's such an impactful virus as it spreads through our ego system. And the same thing happened on Twitter. Because Twitter is so bite size, so easy to share, people share it and because people are sharing it and idea can rocket through the Twitter sphere in just minutes, making your idea more share a bowl without giving up any other element of it is generally a good idea, but too often to make an idea. Share a bowl, we dumb it down and make it less sticky. And it turns out that stickiness is even more important if you want your idea to persist so back to the idea of the measles. The thing is that hepatitis hasn't are not of only two when it's peaking which means that far fewer people are infected by someone who has hepatitis, but it can stick with someone for the rest of their life.

That stickiness means that it is a notable and important disease, not because it spreads widely. It's easy to share, but because it sticks around. So part of what we need to do is not just make our idea in a package that's easy to say. Hey, look at this, but also to have the guts to put ideas into the world that stick with people.

22:45

Hi, Seth. This is Dan from Florida. The question essentially is, Why is it so easy to help others edit their work? But then it's so hard for us to edit our own. If you have any advice, I'd love to hear it. Thanks and have a great day. And thank you for all that you d'oh!

23:0

I think there are three reasons why it might be difficult to edit your own work compared to editing someone else's work idea. Number one is our context blindness that happens all the time. There will be a typo in a block post of mind after I've read the sentence 10 times I still don't see it. So fresh eyes get us through that problem. But more important than that is the idea that we don't see things that are important and others might. We might not see them because we're afraid of them, and we might not see them simply because our point of view is different than theirs. So asking someone to look at something with fresh eyes, who is open to giving us that sort of generous insight that's precious. And then the 3rd 1 is this. We don't like to be wrong. We don't like to be wrong. And editing our own work requires us to admit that we could have made it better. So one of the things that it takes to be a good writer, a good creator is willing to suspend your desire to be right and instead embrace an instinct to be better hope that helps. Thanks for listening. We'll see you next time.

24:21

Hi, it's Bernard at G one, and I'm here to talk to you about this story. Skills workshop. It's no secret that great stories at powerful catalysts for change or that great storytellers have this unique ability to persuade influence and inspire us to connect and collaborate. You know that if you want your idea to spread or you want to match it with people that you hope to serve, you need a better story on dhe. That's why Seth and I created the story Skills workshop to help you to tell better stories and make your ideas matter. I hope. Youll jacket out at the story skills workshop dot com. I just don't think it's possible or probable in today's world to distinguish yourself as an educational institution or is a success seeker at the level of information gathering or information distribution. I mean, this is the information age and you can get a great book, a great essay, a great idea anywhere, you know. And none of us can do that better than the Internet,

right? There is no great thought leader who can out think the Internet like we have data. What all in begets right is it puts you in a context where you're part of a community that says, Yeah, yeah, that's good. You got access to ideas. You got access to information. That's awesome. But when you gonna show up when you gonna face that blank page when you gonna face the possibilities within you, what are you gonna face those fears? I'm not gonna let you gotta show up, and that's the hardest part. And it sounds simple. It sounds very common sensical, but it's the number one reason why we don't write that book.

It's the number one reason why we don't ask that question. It's not because we don't know where we don't have the information. We don't have an environment and way don't have a support network that makes it feel like showing up is possible for me. Not just possible for the success stories I see out there, but I can show Consider the altar MBA.

powered by SmashNotes