Podcast Transcript

Stop Building Useless Software: The Two But Rule

John Wolpert CPO at Valuable · Author, The Two But Rule

John Wolpert has run product at IBM and ConsenSys and wrote The Two But Rule (Wiley). A conversation about constructive objections, identifying underlying needs and choosing suitable technology for product development.

  • Published 23 Jun 2024
  • Runtime 1:00:26
  • Operator
  • Recorded in English
Stop Building Useless Software: The Two But Rule: podcast episode with John Wolpert, CPO at Valuable · Author, The Two But Rule
// The short version
  • John Wolpert’s Two But Rule: never stop at the first but. If you say, but that won’t work, you owe a second but, as in, but it would work if. He calls the underlying discipline momentum thinking.
  • Wolpert argues psychological safety cuts both ways: it must also be safe for senior people to say an idea will not work, ideally with context like, but this didn’t work in the nineties, here is what happened, so you can try again and miss that mistake.
  • His product advice: celebrate a designated but-head, a chief negativity officer whose objections get collected every sprint and paired with second buts, instead of just validating your own assumptions.
  • Drawing on eight years in blockchain and his work starting Hyperledger and Hyperledger Fabric at IBM, Wolpert calls putting sensitive shared data on a blockchain an anti-pattern. He accepts storing hashes and proofs as a use case but argues blockchains cannot support global cash, citing non-zero marginal transaction costs.
  • He argues zero knowledge needs a life of its own: ZK can run on regular computers while remaining computationally expensive. In his view, putting it on a blockchain stacks one extraordinarily computationally expensive thing on top of another.

Intro

Watch this part · 0:00

Kevin 0:00 Hi guys, this is going to be a crazy episode. I’m going to talk with John Wolpert. And Ernesto is as excited as I am. John Wolpert is an esteemed speaker, writer, thinker in technology and business innovation. And as a CEO and product executive and advisor, he has been at the vanguard of technology breakthroughs from the early days of the web to the rise of artificial intelligence.

Kevin 0:23 John is known for founding Flywheel, a pioneer in the ride-hailing industry. And his work at IBM made him a key figure in the evolution of open source software, blockchain and AI. He has co-founded global R&D consortia and industry standard bodies, and his thought leadership in open innovation has been showcased in the Harvard Business Review.

Kevin 0:44 John has led countless new venture workshops and spoken before at the European Union and Australian Parliament in his mission to help organizations work together to solve hard problems. So I’m super excited to have this conversation with John. And I really can tell you, every time his wisdom and, you know, vision through all that nonsense is just incredible.

Kevin 1:13 So without further ado, let’s dive in.

1:16 Wavect, the Web3 software company that understands what you want.

Kevin 1:24 Hey John, thanks for having me. Well, first of all, you have written a really cool book, The Two But Rule. And as we have worked together before, I really started using it from the time where you explained it to me and it really made an impact in our business. So first of all, since most of our viewers might not be familiar with it, would you mind sharing what The Two But Rule is about and what kind of brought you to this?

The Two But Rule

Watch this part · 1:25

John 1:59 Sure, Kevin. It’s great to see you and thanks for having me on. The Two But Rule is a pretty simple idea at the start. It gets deep though. The Two But Rule starts with simply saying, but it won’t work. Being negative, saying somebody presents you with their intentions to do something, overcome a problem, capture an opportunity, uh, they have an idea.

John 2:22 And what, what do we say? What? But that won’t work. But I don’t like that. But we can’t afford it, right? Um, you experience this. Uh, I experienced this, you know, in talking with my wife sometimes. But we can’t afford it. But we can’t do this. But, but, right? So we’ve lived in a culture. Certainly as a Gen Xer, I, I lived in a very strong, uh, one-but culture, right?

John 2:44 You know, the boomers would come in and drop a one-but bomb on us. You know, but we don’t want to do that. But, you know, but stay quiet and do your job, right? That sort of thing. So we didn’t like that very much, and so what did we do? We turned around and created a no-buts culture for you all. Sorry about that, because if there’s anything that is a bigger momentum killer than a one-but culture, it’s a no-buts culture, right?

John 3:10 So you have a no-buts culture that where people are afraid or feel unsafe or just don’t even know to um, to challenge an idea. Um, you know, we, we have all these phrases out there, like no killer phrases in brainstorming, and there’s no idea, no, no ideas are bad ideas. That’s a really bad idea. There are definitely bad ideas.

John 3:33 We should love our bad ideas. Every idea, the mythology that there are entrepreneurs that are just stubborn and dogged and pursue their original idea in spite of opposition. Maybe it happens from time to time, but in my experience, there’s always a deeper story behind that mythology where, yeah, no, their idea was terrible, and then they evolved it when they came face-to-face with opposition.

John 4:02 Imagine the Apollo 13 mission, right, when the crew was in danger and the command module exploded. And their first idea was to turn the ship around, burn the main engine, get back to Earth right away. And imagine what would have happened if, when an engineer said, but that won’t work, the engine is probably damaged, somebody had said, oh, don’t be so negative.

John 4:33 No, it was, yeah, that would have killed the crew. Turns out later they found out that, yeah, that would have been a very, very bad idea. So instead they said, but we can slingshot around the moon, get them back to, you know, use a lot of gravity, get them back that way. And then there was a whole series of butts after that.

John 4:48 But they’re gonna, they’re running out, their, their, their CO2 scrubbers aren’t working in the LM. But we could fashion a Rube Goldberg machine to fix that. But the, you know, there are so many butts, right? Life is a chain of butts, right? But that won’t work. But it would if. But that also won’t work.

John 5:06 But it would if. And in my experience running innovation labs and research organizations and product teams, uh, you know, five rounds of The Two But Rule, right, is, uh, is a good recipe for coming up with something innovative, maybe a patent or two. Um, and, uh, I’ve had experience with that. So that’s, that’s The Two But Rule in a nutshell.

John 5:30 Underneath it, there’s a lot about intentions and listening for the needs behind why somebody wants to do something and why you don’t want to do it or what are the needs driving your need to oppose it. And then finding a creative way of squaring those things, right? You say, but I don’t want to do that, but I can see why you want to do it and I can see why I don’t want to do it and where can we meet in the middle and square those two things.

Kevin 6:00 That was a beautiful explanation. And one thing that I really like about this is it’s not just great for discussions, right? But it’s also great if you just talk with yourself, like evaluating something, because it forces you to be more open-minded about a certain problem statement, let’s put it that way, right?

Kevin 6:21 So you really have to think, oh, well, I, I really don’t think it’s good, but under what circumstances could it be better or whatever? So that’s kind of a really cool shift that helped me as well.

John 6:39 Yeah, I think that’s the, for me, I think most of us live life afraid of our butts, right? Right. I’ve sat in that chair right there in my little thinking chair and run from my own butts so often. Right. Where I’m like, oh, I want to do this. I want to build this. I want to try this. But. And then I’ll run away from them.

John 7:06 And, you know, I waste tons of time. Just if I’m mindful, I realize that I’m just, I’m frozen in place, afraid to face those butts. And I wrote the book about it, right? So it’s, but in a two-buts culture, right? When you’re habituated to two buts, you say, oh yeah. Oh, hey, hey buddy. Thanks for that.

John 7:27 You know, that’s a great but. Let’s, show me all your buts, right? And so that, we call this momentum thinking, which is the clinical term for this. But I also wanted this to get into the culture of more teams, more companies, because if people expect your second but and you’re habituated to providing the second but, they’ll give you a chance with your first but, right?

John 7:53 As opposed to, you know, it’s very vulnerable thing to present, you know, hey, I want to do this. And somebody says, but that won’t work, right? I remember a team I was running at IBM that happened and, you know, a new hire stepped up with a, hey, what if we did this? An engineer on the team went, but that won’t work.

John 8:14 Mic drop. And then I said, but it would work if? Now, ideally, the engineer would say this already, right? I wouldn’t have to prompt, but this is [unclear]. And so I asked him, but it would work if? And he looked at the ceiling and went, but it would work if gravity was different. And that led, and then not a minute later, another engineer popped out of their seat and they had a terrific, they were like, what if we did this?

John 8:43 We didn’t change gravity, but it gave the second engineer a new context, a new way of thinking about the problem. And that led to a couple of patents and a project that got the attention of the CEO of IBM. So yeah, that’s momentum thinking. Called it The Two But Rule cuz I figured that would just be catchier and and more likely to get people to think more about it.

John 9:04 Because once you’ve seen your butt, you just can’t unsee it. I mean, it’s, it’s, yeah.

Kevin 9:11 Well, the cool thing is, I’m just remembering Jeff Bezos saying, you have a great company culture. If the most, let’s say, as the newest hire, or youngest, most inexperienced, uh, engineer or person on the team can trump the most senior person on the team with facts, like, and I think that’s also some kind of a, a great approach to induce that in some kind of way, right?

Kevin 9:45 Because everybody can come up with a somewhat silly but as well, right? Which is part of your strategy. So that kind of opens the gates for anyone to contribute. And,

John 9:59 right, the rule is you have to bring a second but. It doesn’t have to be a particularly good one. And then the team has to remember that they can also two-but that. But that’s not a very good idea, but it would be if, but that also is not. If you can sustain it for long enough, you’ll come up with something.

John 10:18 I had a family discussion just the other day with my wife and we were talking about this and I had a reminder because she was like, I came up with a terrible second idea, and she’s like, that’s bad idea. Like, of course it is, that’s the point. It is definitely a bad idea. That’s why I said it. And she’s like, oh, right, right, yeah.

John 10:38 And then we went, we found a really good solution to a problem with birthday parties, I think it was [unclear] this particular problem, problem. But yeah, yeah, it doesn’t, doesn’t matter what it is. It could be life sciences or climate change or, yeah, family birthday party. Um, yeah, so that, that’s that, you know, just habituating yourself to that, um, and, and having a culture that expects it, uh, makes it safer.

John 11:06 But you said something about how this empowers, uh, newer, younger employees. There’s a lot to be said about making safe spaces for employees, less experienced ones. But I found that the opposite is an interesting thing to look at. Today, it’s unsafe for most managers in any company of size to tell any employee that their idea is not good, right?

Creating Safe Spaces for Employees

Watch this part · 11:10

John 11:37 And there’s a book by Amy Edmondson, a Harvard professor, great book, actually several great books by her, but she’s really into this idea of psychological safety, which makes a lot of sense, but it can be misread as, hey, you know, you have to make everybody feel safe and validated and stuff like that.

John 11:56 Like, no, your idea is a bad idea. I’m not doing you any favors by [unclear] telling you it’s not a good idea. The example that’s often brought up is, you know, there are a couple of cases where a, a senior, say, pilot didn’t listen to the junior pilot and disaster occurred. But what we often don’t talk about is what about the case where the senior pilot disregards their own judgment from years of experience and goes with the less good idea of the junior pilot, and that causes a disaster, right?

John 12:27 So you can’t just apply that in a blanket way. How do we give, make it safe for a senior person to say, hey, uh, great idea, but not such a great idea, but this won’t work? And one way to do that is to say, but this didn’t work in the 90s, but here’s what happened, so you can try it again and, uh, and maybe make you miss that mistake.

John 12:52 Um, so there, I think it works in, in, it’s hard to present your butt to anybody, whether you’re a senior person or a junior person, I think.

Kevin 13:04 That’s interesting. Well, when we talk about like where to apply this Two But, Two But Rule basically, like I’m pretty sure there are certain areas of your life or career where The Two But Rule has a bigger and, let’s say, is more impactful than in others. Like, do you have some kind of, what is your experience with it?

John 13:33 I think it works best in team environments where you’re trying to wrestle with a gnarly problem, right? Where there isn’t a clear answer. You’ve got to go left or right, and there’s no way to know for sure which way to go. And again, the great silly but for that is, hey, you want to go left, but I don’t want to go left, but we could go right.

Where the Two But Rule Has the Biggest Impact

Watch this part · 13:35

John 13:54 Well, you might say, but we could both grow giant long legs and go left and right together. And that’s silly, but it tells the person that, hey, you listened to them, and that whatever you’re going to do, you’re going to do it together. So there’s utility in even that silly but. The other very useful thing is, and I think this is maybe the mission, is to help the buttheads, right?

John 14:20 How many people, how many folks are watching this right now feel like they might be getting voted off the island or becoming a pariah or a Cassandra, somebody that nobody listens to, or either because they are seen as too negative because they chime in with a lot of butts, or because they are not feeling comfortable about presenting their butts and they let a lot of bad ideas slip by them and they become ineffectual.

John 14:49 Right, there’s a lot of people on both sides of that that are in a terrible place. I mean, the halls of mental health must be filled with buttheads of, you know, people that are one-butters, right? Because it’s not a fun job, but people don’t like it. They don’t like it when, when they hear but, but, but.

John 15:05 Um, so can we turn that around and save the butthead, right, and say, oh yeah, [unclear], he’s our official designated butthead because he always comes up with two butts, right? Uh, that’s, that’s, in fact, if you’re doing lean startup, there’s a story in the book about how we missed a trick with an experiment we were running in the market.

John 15:25 And we missed it because we validated our assumptions rather than using that experiment to look for the additional buts that were out there lurking for us. And we missed a big one. And it was a costly mistake because we were so happy that one part of the experiment validated what we thought rather than going, oh, but what else is gonna go wrong?

John 15:48 Oh, what else is this experiment telling us about the problems with this approach? And we missed a really big one. And if we just had a designated butt head on team, who, you know, the chief negativity officer, right? If we could celebrate that person, right? And say, yeah, we love that you are good at finding problems.

John 16:11 Let’s get all those buts on a wall and at the end of the sprint, let’s pair them with a second but and then find the ones that we can do something about or explore and go to the next sprint. I think that’d just be a lot more fun and a lot more productive.

Kevin 16:28 And it gives you a metric, right? Um, for those that are not as disagreeable, they have to come up with something, but those, as you said, that are too disagreeable, maybe they also know, like, I have to come up with the contrary opinion as well. So it’s kind of, uh, as you said, momentum thinking, and that’s the beauty of it.

John 16:51 In fact, the, the, uh, this is not in the book, but, um, in working with teams since then consulting, uh, I’ve, somebody pointed this out and I think it’s brilliant. If you, um, are a person that, that chimes in too quickly, right, that, I don’t know about you, but when I, when I, um, feel like I’ve, I’ve jumped into a conversation too quickly, it’s usually because I’m worried that I’m going to forget what I wanted to say.

Chiming In Too Quickly

Watch this part · 16:55

John 17:20 You know, that something you’ve said triggers something in my head, whether it’s negative or not. And, and then that, that leads to, uh, you know, then you become that jump-in person. There’s a lot of people like that. Um, I was talking to somebody about this and they’re like, yeah, I’m from New York, that’s normal, right?

John 17:40 Yeah, so there are cultural differences in timing. But, um, on a team usually you need to give people space and time and, and you have to get the rhythm right. And for some people that’s really hard. There’s a lot of ADHDers out there that find it very difficult to get the rhythm of a meeting with more than one or two people right.

John 18:02 The observation was that if you wait to provide your one but until, if you wait to have your second but formed before you provide your first but, you will not forget your first but because you’re formulating the second one and it generates all this neurological, this neuron activity, you’re not forgetting that first but.

John 18:25 You can wait. You can get to the end of the meeting and it’ll still be there. And that gives, if you get habituated to that, it gives you time. It makes you more thoughtful. It opens you up to listening to, okay, well, the second but’s got to come from this other person’s needs. What do they really need?

John 18:43 Okay, well, actually what they’re not saying is what their real need is is that they need to be heard on this something, you know? Okay, but we could do that, right? But now you have something that can, that’ll last, that’ll last till the end of the meeting or even after the meeting, you’ll bring it back up.

Kevin 19:06 Quick intermission. If I could ask you for one single favor, it would be that you hit subscribe onto this channel because it helps our channel more than you can imagine. And, you know, the bigger the channel gets, the bigger the guests get. So thank you very much for watching. And let’s continue with the episode.

Kevin 19:27 Well, obviously, you can apply this method in a lot of ways. I’m wondering when it comes to product management, product development itself, like building or launching a product is a long, long, long process. After the launch it continues, right? Um, like how does the application of this approach maybe change throughout the process, or is it mostly really just for discussion and when there is something like a dispute or something then it’s great for settlement or something like that?

Does the Two But Rule Change Product Development?

Watch this part · 19:30

John 20:05 Well, it’s certainly great for alignment, as you know, and I certainly know for many years, there isn’t a team that doesn’t go through an alignment crisis every sprint. It’s just a thing that happens. Humans get offside. You start to get this just mental genetic drift from whatever somebody’s original thought was, and this happens for as many people as are on the team.

John 20:35 So alignment, certainly, it’s good for that, right? Say, okay, but I’m starting to think these new thoughts, but we want to stay on track. But we can stay on track and embrace the new thoughts if we, right, there you go. So you’re applying the needs, right? We need to stay on track. Well, you know, it gives me anxiety to think about zigzagging all over the place.

John 20:57 We don’t want to be that company, but at the same time, we need to be responsive. That’s a gnarly problem or a wicked problem, as they call it. Right. There is no right answer. It’s balance. Balance point problems are all good two-but problems to deal with. So that’s one side of it. The other side, and I mentioned the lean startup.

John 21:16 So there’s a chapter called Leaning into Your But where you can apply instead of the five whys. It’s kind of like the five buts. You know, you want to lean into your but on lean projects and experimentation. And then the other part that’s really important for product management, I think, has to do with the product itself.

John 21:36 So for example, I’m really fascinated right now with a powerful two-but problem, which is we need to share, but can’t share. I’ve been fascinated with this problem for almost 30 years, I think, certainly 25. The need to share, but can’t share problem pops up everywhere. You’re a startup. You’re pretty sure you need a partner.

John 21:57 You cannot tell the prospective partner. First of all, you may not know what the ideal partner is. So, but you can’t put it out on LinkedIn that this is something you need because you’re exposing your intentions. You can tell your [unclear] about, you can invent something and tell everybody about it, patent it, whatever, right?

John 22:15 It’s very scary to tell people about your intentions. Hey, we intend to do this and we have a gap between what we want to do and what we can do. Companies find this to be extraordinarily terrifying and rightly so. Anybody, you know, you can’t protect intentions and intentions are the action verbs of innovation, right?

John 22:36 I mean, inventions are the nouns. What I intend to do with something is the action verb, right? Here’s my invention, a pen. I can stick it in your eye and now it’s a disruptive innovation. And I cannot tell you about that or anyone else before I do it or you’re not going to sit there, sit still while I do it, right?

John 22:55 So that’s, the intentions are tricky, and especially across different companies. So this is a great example of a problem that needs products, needs solutions, and you have to apply The Two But Rule to it. You say, but we really can’t share, but we could coordinate if the need behind our sharing is, is finding sources of assistance and help and stuff.

John 23:22 Can we use things like zero knowledge cryptography on one hand? Can we use headless vectors on another to be able to find coordination opportunities without exposing data to each other directly? I think that’s a really interesting space, right? Where not even the SaaS provider actually has your data, but they can still find connections for you and also allow you to coordinate in a supply chain, in executive recruiting.

John 23:52 All these are we need to share. I’m a CEO. I want to leave my company. You’re the board. You want to fire your CEO. Neither of us can tell anybody except our recruiter. Right. That puts the recruiter in a very delicate position.

Kevin 24:06 Yeah. Now let me apply your Two But Rule. But is that really such a huge pain? Because when looking at LinkedIn, you can already hide, for example, your intentions from your current employer. Of course, they can find out if they want to. So it’s not bulletproof. But isn’t that enough, basically, to solve that pain?

John 24:34 Yeah, it is. It is. In that particular case, of course, you know, you’re always sweating a little bit that somebody’s going to out that data. So we’re worried about that. So, yeah, in these sharing situations, you need to trust a provider, right? A recruiter, executive headhunter, a SaaS, a LinkedIn.

John 24:58 And that’s, yeah, it becomes a trivial problem if you can trust the intermediary. Like, you know, remember when you were in high school and you were in love with so-and-so and their friend was dating your friend, but you know that your friend is a big mouth and you can’t, you could really get, you know, it would be very handy if you could just say, hey, can you get, put me next to them in this date with your, when you’re out, you know, at this movie and be like, no, they’re definitely going to blow it for me, right?

John 25:26 So, I mean, it’s very delicate situation, right? But there are deeper ones like supply chain, for example, where, you know, we need to figure out supply chain risk, single source risk, things like that. And the suppliers will not, no matter how much power you have. And I’ve been in a thousand kinds of projects like this where a very powerful company thought they had enough power to get everybody to give them their data.

John 25:50 And it turns out, no, no, they don’t want to give them the data. So how do we coordinate? but we need to know where all the bad radishes are or where all the contamination or maybe there was a poisoning event or salmonella or something like that. Or we know that there’s, we don’t know where we’re going to, our production line is gonna come crashing to a halt because one vendor of a vendor of a vendor of a vendor is a single source contract coming out of say China.

John 26:21 And there’s a disruption in that particular thing. And now our jet is three months behind and millions of billion, hundreds of millions of dollars over budget, just because of a one tiny little part, four or five layers deep in a supply chain. To be able to visualize that, find it, predict it and deal with it.

John 26:43 Yeah, if you could have all the data, it’s a trivial problem. The problem is companies don’t want to give it to you. So I find that to be a really interesting two-but problem, right? But the companies, you know, accept the fact that the companies have needs to not, you know, if you’re a chicken farm company, you don’t want the supermarket chain that has power over you to know where all your chicken farms are.

John 27:09 Right. But they need to know if there’s a contamination, how do you, and we also don’t want to have a big honeypot of data in the middle of us all, right? IBM, I was at IBM, we tried that many times over the years. You know, turns out nobody wants to give us the data either, right? So how do you not give, provide the data but still coordinate?

John 27:34 It’s an interesting problem.

Kevin 27:35 Yeah, well, definitely something that is being worked on for a long, long, long time. And, you know, we see it in a lot of things already, right, with ZK, as you mentioned, and all these commercialized data projects, data sharing projects out there. There’s a lot of going on in that space.

John 27:58 Yeah, I mean, we thought that blockchain was, that’s why I got involved with blockchain years ago, is that we thought that that might have been an approach. It turns out it’s an anti-pattern. Putting your data on a big digital nudist colony is kind of the opposite of what you want to do with that kind of problem.

John 28:16 Uh, so, you know, I mean, even with, uh, obfuscation, in the world of AI, I will make you if you put your transactions on a blockchain. Do not do crimes on blockchains, kids. Uh, they will find you. Uh, use mixers, you know, we’ll still find you. Um, so, and, you know, and there’s scaling problems with that particular approach.

John 28:37 Um, but the problem space, like a lot of things in Web3, the problem is legit. The solution, it turns out, to that problem, that problem set, like, yeah, we do want, we want to have a lack of, we don’t want to be locked into a vendor. We don’t want to, we don’t want Facebook to own us or what have you.

John 28:59 Um, we want to be able to move our data without losing our connections, our SEO. You know, we don’t want search engines to lose us. Um, well, one way, uh, Substack. Um, I have my own domain. Substack has a custom domain. I paid them 50 bucks. And now if I were to move all of my Substack articles somewhere else, it’s just a 301 redirect.

John 29:24 So I didn’t need blockchain for that. I just, it’s just a policy that the company had that you’re not gonna be locked in. We did that in the nineties with phone numbers in the US. And I think Europe did it as well, where we have done number portability. We just decided that by regulation, we said, all phone companies have to be able to allow you to take your number with you if you move to another carrier.

John 29:49 Before 1997, you couldn’t do that. We didn’t use a blockchain to fix that. We just decided that that was an important thing. So lock-in, I think, is important. Decentralization for decentralization’s sake, that’s where I think we went wrong. I think that what we need to do is focus on the problems, why we have those problems, what are the needs that we’re trying to address with, where we think that Web3 or blockchain would solve it and then say, yeah, but it doesn’t scale, but it’s actually kind of an anti-pattern, but we could still achieve what we need, even if we don’t use a blockchain.

Kevin 30:29 Use the easiest technology for your problem set. Absolutely makes sense. Well, as you said, when it comes to data sharing, I mean, these kinds of things specifically, [unclear], like I mostly agree with a lot of things, you know. Of course I’m selling blockchain, as you know, but as you can see, also highly critical when it comes to for what use cases you apply it.

Kevin 30:59 For a lot of things, it just doesn’t make sense.

John 31:02 I still think that blockchain is a good, it’s a public, large public linked lists are a good thing to store hashes and proofs on, right? And Scott Stornetta has been doing that since 1995 with the New York Times classified section. It’s a perfectly good use case. I need some way of proving that this hash of some data I took a hash of at some point in the past, that the data is still, hasn’t been tampered with.

Does Blockchain Make Sense?

Watch this part · 31:05

John 31:28 And I need to know that the hash itself hasn’t been tampered with. So I need something that’s really tamper resistant. And if it’s a hash, well, I mean, you don’t really get much data out of a hash. So I don’t mind the idea of plopping hashes or, you know, Merkle trees full of hashes or head end of a Merkle tree like Mina.

John 31:49 I still kind of like Mina. I’d love to fork Mina and find a way to do Mina without having a gambling token powering it, right? Because, you know me, I’m not into that. A friend of mine came up with an interesting way of using stocks, like legit stocks, as a way, as a form of staking for, you know, I think we call it stock chain or something, uh, where you, you know, you don’t use a cryptocurrency token, um, and try to convince people that the coin go up to, to run the, uh, to secure the network.

John 32:21 You could actually stake your own, you could stake stocks into a mutual fund type of a system, and that would work. That would actually work, right? So if you could run a Mina without crypto, because I don’t like crypto, and you could run that in such a way that you could say to anybody, here’s my Merkle proof of our state of the shared data that we have.

John 32:43 I’ve got some data in my system. You’ve got some data in your system. And we’re going to run a proof that says this data that we have is the same, that my credit is your debit, and that the rules that we use to get there are correct and followed a set of rules. Right? And I can attest to that and I can put that proof in, I can send you the Merkle proof of that.

John 33:08 And all you have to do is check the head end of a Mina blockchain. And you’d be able to say, yep, yep, you definitely, that debit and that credit. And yeah, you didn’t loan the guy over the usury law in Texas. So yes, I will insure your loan. And I didn’t have to give them the data to do it. I think that’s a perfectly good use of blockchain.

John 33:29 It’s just kind of boring. It definitely doesn’t make crypto degens get rich, but it’s a pretty good use of blockchain because it can scale to handle that use case. Blockchains can scale to handle that use case. Being the world’s currency system, never going to do it. When we can make a blockchain do that, we will also have warp drive and that’s not hyperbole.

John 33:57 I don’t know. Let’s be honest here. We could get Leslie Lamport, the father of distributed systems, on the phone. I’m pretty sure he’d say that. Causality is causality, and the speed of light is a limit. So if you can break causality and actually handle, you know, make a replicated singleton scale, then that’s great, but then we would also, we would be able to break the speed of light.

Kevin 34:26 What you mentioned with using stocks, basically, that reminded me just of a lot of these projects that try to use at least a different asset on a different chain as, let’s say, for proof of stake consensus mechanism. So it kind of, I think the technology is already there for these kinds of use cases, right?

John 34:53 Yeah, but you’re back into the labyrinth, right? I mean, you know, in fact, you think about correspondent banking is a decentralized system. There’s all those banks and they all have their own ledgers, right? And the, and Swift and other things try to keep them in sync, which is what the central block, instead of central bank, now you have a central blockchain, right?

John 35:10 You know, they’re handling bridges. Where do all the problems with crypto happen? At the bridges, or most, a lot of them, right? And of course, yeah, what we’ve learned is that, you know, what, whereas you can say that the, that, um, say Bitcoin has not been hacked and that the tamp, you know, tamper resistance has been proven, there certainly has been an awful lot of crime and, and hacking on the edges.

John 35:34 So it didn’t solve that. Um, lots of fraud anyway. Um, because at the end of the day, you know, the, the blockchain has to meet the real world somewhere, and so, yeah, you, you’re back to the, what I always found in eight years of blockchain was that every time you thought you’re on your way out of the labyrinth and you’d solve the problem, figured out something, you were back in, it would walk you right back into the labyrinth, right?

John 35:58 So we were trying to get away from centralization. We are delivering a terrifying level of centralization in the name of decentralization. The crypto hegemony is real. Uh, you know, you know, as we’ve seen, um, the, the price is inflated, is, is being maintained by people that can afford to wash trade and do some things to keep it up there.

John 36:21 Lots of manipulation. All the things that we wanted to get away from we are delivering in spades in the name of getting away from them. I don’t like that. Um, yeah, so that’s, uh, but that’s the problem that I found with the blockchain, is that every time you try to maintain the principles of blockchain, you wind up with either succumbing to the very things that you say, oh yeah, yeah, yeah, it’ll be faster if we have less decentralization.

John 36:54 Yes, Solana is faster than Bitcoin and faster than Ethereum, but it’s also less secure. So these trade-offs are fundamental. Is a linked list fine? Sure. Yeah, I like linked lists. But do I think that you decentralize all the things simply to decentralize them? No. Right tool for the right job, as you say.

Kevin 37:19 Well, as I said, decentralization is a tool by itself. So if you need it for some kind of reason, I definitely think there are certain cases. Just think about, that’s my butt basically, but not so stable governments, not so stable countries. Just those edge cases where you actually can’t rely on those.

John 37:46 And then here’s my blockchain, but here’s my gun, right? Gun trumps, right? So does that really solve? Again, this is where zero knowledge cryptography and digital identity definitely need, just don’t need a blockchain for it, right? Maybe you can anchor attestations and DIDs and stuff. Maybe it’s fine.

John 38:11 But at the end of the day, what we’re doing right now in the States is implementing digital driver’s licenses and that sort of thing. And it’s all just coming off the secure enclave on your phone and no blockchain involved. You don’t need any crypto to do it. So yeah, digital identity, secure digital identity against somebody making you, right?

John 38:30 So, you know, you definitely don’t want the bad guy to know that it’s you. Journalism, you definitely don’t want, but it’s not a panacea for that. I mean, really what we have to stay focused on is the problem, right? Getting journalists, less journalists killed is the problem to solve. It’s not, hey, blockchain, let’s see if we can save journalists with blockchain.

John 38:56 There’s a very nice person in the blockchain space who I quite like in many ways, but they would drive me crazy with this one line. They would say, we are going to save the world with blockchain. I’m like, can we stop with this? Can we just start with save the world? And let’s focus on that. Just focus on the save the world part.

John 39:19 I mean, I’m all in on that. I don’t know that we put a lot of constraints if we say with blockchain, you know.

Kevin 39:26 I thought that was funny. I mean, you see that with a lot of things, right? It’s not just blockchain, it’s also AI, quantum computing, all these things where people, we see that when they come to us with projects, I want to use Web3, I want to use AI, I want to use that, that, that. But instead, oftentimes you have to scratch all these things and tell them, what do you want to do?

Kevin 39:50 Do you want to raise money with this? Do you want to get your first paying client? You want that, that, that, that. Then let’s try to figure out a way how to spend the least amount of time and money to get there.

John’s Time at IBM

Watch this part · 40:00

John 40:02 You know, when I was at IBM and, you know, we were running, you know, we started, uh, uh, Hyperledger and Hyperledger Fabric, I would, I would be my own worst enemy or, you know, I’d be like, I don’t know, it was weird. I could, I could get a sale out of a big bank just by telling them, by like negging on it.

John 40:18 Like, say I’d be like, why are you using this? And it’s my product, right? And I’d be like, why are you using my product? You shouldn’t be. And they’re like, oh, now we really, really want to use it. And the funny thing is I, I, if I had a nickel for every time, uh, I had, uh, you know, some company, uh, usually big, big company, uh, you know, the team, and I would challenge them with this, with this, but a nickel for every time that they said, well, we don’t really need it, but we’ve been trying to solve this problem for 10, 20 years.

John 40:48 And if we call it blockchain, the boss will fund it. I mean, that doesn’t happen anymore. Nobody cares. In fact, you calling something blockchain will kill the project, but in, in the, Yeah, I think that may be the thing that will kill crypto faster than anything else, is that crypto requires hype. You cannot, crypto cannot survive.

John 41:09 If crypto, if a blockchain could support a cash use case, global cash, I’d say that’s, I would have a different point of view. But we know it can’t. And don’t talk to me about Lightning. It’s not going to, no. No, because again, the problem is that the marginal transaction cost of a transaction on any kind of blockchain is non-zero.

John 41:34 Whereas in even the worst of banking systems, the marginal cost of a transaction limits to zero. The banks charge you a fee because they can, not because they have to, right? And so these are basic problems with the cash use case. If it could be cash, I would say, okay. Or if we said every token was an actual security, I’d be okay with that, right?

John 41:58 I don’t like fleecing grandma. I don’t like opening up all the same loopholes that we had in the 1800s that fleeced grandma that made us go into creating the kinds of regulations that the SEC did in '33 and '34, which still are valid today, by the way, right? But if we said, yeah, every token is actually, yeah, it’s an investment contract.

John 42:19 And we’re going to keep the track of that investment contract on a blockchain. I got no problem with that. Just call it what it is. It’s an investment contract.

Kevin 42:26 Um, something really interesting now that brought me to a point that I never actually thought about. What if, I think that, uh, thesis you might like. What if blockchain [unclear], basically banks are able to charge those fees, right, which are really high oftentimes.

Making Financial Infrastructure More Efficient

Watch this part · 42:35

42:46 [unclear] for a million dollars. As high as buying a pack of gum with Bitcoin and costing $200 for the transaction. But yeah, okay.

Kevin 42:58 If you transfer huge sums from the US to, I don’t know, China or wherever, or just in Europe, you already pay a nice fraction of that, right? And I’m just thinking, what if, you know, just from the sake of the goal of making the financial infrastructure more efficient, just by blockchain existing, forcing banks to lower their fees, that could be, you know, like...

John 43:29 Yeah, no, if the ultimate thing is that crypto kind of becomes dark web money, and it’s not a thing that most people deal with, but it scared the crap out of the banking system and it got, and it made the banking system get, get their act in gear, yeah, I think that would be, yeah, there’s nothing wrong with that.

John 43:46 Um, and the, the, there’s a really good book to read if anybody’s into this stuff called Moneyland. Uh, Moneyland’s a really good book. It’s not about blockchain, but if you look at the dates for when a thing called FATCA started making it very difficult to use Swiss bearer bonds, untraceable bearer bonds to move money across borders with impunity.

John 44:08 That was around 2008 to 2014. What was coming up in 2008 to 2014? Yeah, I don’t think Bitcoin is digital cash or digital gold. I think it’s digital variable-price bearer bonds for people who have either legitimately or otherwise a really strong need to move money across, large fistfuls of money across borders with pseudo-impunity and avoidance of tax.

John 44:37 Yeah, that’s a real good use case for it. Cause it, you know, it’s relatively small number of transactions, large amounts. And thing is the kind of folks that need that often aren’t the kind of folks you want to know very well.

Kevin 44:58 What shall I say? You know, nobody knows for sure. At least, you know, I always try to keep just open, but, um, like as mentioned before a couple of times, use technology where it makes sense. Blockchain, absolutely agree with you 99, 98 percent of the time, and I’ll tell that our clients as well, doesn’t make sense, right?

Kevin 45:26 Or it’s just a solution by itself, you know, for its own problems. But, um, as you also mentioned, it’s maybe like decentralized identity could be, or at least, you know I, I consider ZK part of blockchain, for example, right? Because

Is ZK Part of Blockchain?

Watch this part · 45:40

John 45:44 I don’t, I, I really wish we would get away from that. ZK needs a life of its own. ZK works. Computationally expensive, but there’s nothing in the laws of physics that prevent it from, uh, delivering on its claim, which is that you can prove anything under [unclear] or IP under zero knowledge. Um, and, you know, there’s some things are harder than others, but none of it is fundamentally impossible, right?

John 46:10 Even, you know, even, even conditionals can be done. And you know what’s really good to run them on? Regular compute, right? I got a computer, you got a computer, not a blockchain, right? But if you have an SAP system and I have a Microsoft Dynamics system, this guy’s got a spreadsheet. We can do things on regular computers with zero knowledge.

John 46:32 Putting zero knowledge on blockchain is like putting an extraordinarily computationally expensive thing on top of another extraordinarily computationally expensive thing, which makes not a lot of sense to me. Although thank you gambling money for paying for so much zero knowledge research. Thank you very much.

Kevin 46:51 So here’s my but. What about the verifiers? Why don’t we, you know, basically it’s a hash that you put on chain. Say, well, don’t tamper with that hash, like with the verifier so that the proof is actually correctly validated. If you have it on a computer, you definitely can change that.

John 47:09 Totally can do that. You absolutely can generate your zero knowledge proof and do your circuit on one computer, digital signatures. We know how to do that. It’s fairly trivial, but then yeah, where do you put the proof? You don’t need to verify the proof. You can just store it on a tamper resistant system.

John 47:30 So, and you know, if you want to run a verifier on a blockchain too, cool, that’s great, but you don’t have to. And it’s expensive too. So why do it if you can do it more efficiently on regular compute?

Kevin 47:45 That’s maybe now really a great but. So basically just trying to understand, do I really need to make sure the verifier is not being tampered with? We both know that for 99% of the case, of all cases, it’s totally fine to just have the verifier in a single regular JavaScript file or whatever on your own computer, on a server.

Kevin 48:11 But maybe.

John 48:12 Well, you can also with like SBOM, uh, like a, you know, software bill of, of, of, uh, materials or bill of lading. Um, so there are ways of being, of achieving the goal of what we want with that simply by, uh, saying, okay, the verifier is a high-performance system and here it’s centralized, but it’s also observable, right?

John 48:36 And we can state-hash it continuously and we can have people observing that. And that, for certainly for a bunch of companies trying to make sure that they’re not playing shenanigans on each other, it’s perfectly fine. And, you know, yeah, there’s just a lot of it, it’s, I found myself having a very difficult time finding use cases where I, I need supreme decentralization on every single thing.

John 49:03 I just don’t see that.

Kevin 49:06 But yeah, just you mentioning that the verifier, things that you mentioned somewhat go into the direction. So it’s always about like how much resources do we need to put in as well? That’s also kind of a framing I really like. Blockchain is an existing infrastructure. When you have built the semi-decentralized systems yourself, like coming up with a logic concept for that, it maybe requires more work than just deploying that simple verifier on chain.

Kevin 49:38 So maybe that could be useful.

John 49:42 Certainly, for, the problem is we’ve been sucking in a lot of journeyman new developers, right, who get excited about the new thing and it, the POC works fine and it’s exciting. It’s easy, you know. It was not, it wasn’t always that easy, but, you know, you’re like, oh, I’m gonna use a smart contract.

What About Smart Contracts?

Watch this part · 49:45

John 50:02 Anybody who’s been around knows that a smart contract is basically a stored procedure on a, on a ledger. Stored procedures we’ve been doing on Oracle systems for a thousand years, since the 90s. We didn’t like them then. Stored procedures are really not efficient, not a good way of doing business logic on a, on a data set.

John 50:24 It’s not a great way usually, right? And so, but we did, you know, Vitalik said, hey, let’s do smart contracts on a blockchain, and it opened up this whole thing. And sure, yeah, if it could scale, um, or if we didn’t then suddenly go out and, and create a bunch of securities and not call them securities and fleece a bunch of grandmas, you know, then that would have been a super duper, right?

John 50:50 But it turns out that stored procedures as a design pattern isn’t awesome if you can achieve the goal some other way. But now, yeah, there’s a lot of people that are excited about smart contracts because we’ve been telling them to be excited about smart contracts. And I’m here to say, hey, think for yourself and don’t let the blockchain hype masters, you know, fool you into supporting something simply because they want their coin to go up.

Kevin 51:22 It’s always, if you go right at the beginning, what intentions, right? That, um, that’s in fact really a sad thing to see that many people, you know, we don’t preach [unclear]. They preach what they aren’t [unclear] are not by themselves, right? So it’s kind of, um, they don’t stick to the vision they put online and just do something else basically, right?

Kevin 51:53 On the backbone, they have all these VCs and then they do let them dump on retail, on people. All of these things ultimately are mapped to, you know, bad intentions.

Why It’s Hard to Go Against Your Wallet

Watch this part · 52:00

John 52:05 It’s hard to argue with your... It’s hard to go against your wallet, right? And I spent eight years earnestly trying to find some not crypto way of using a blockchain. And at the end of the day, when I couldn’t, when I was out of butts, I said, hey, I’m out of butts. And I said it openly and not everybody loved that.

John 52:25 It’s funny, the degens loved it because I spelled blockchain correctly and that’s all [unclear] wanted. But the guys trying to sell enterprises on this stuff, I don’t think they had a big sense of humor about it. I got a little bit of blowback from them. But the interesting thing is one day I was on a call with a professor and I won’t say who it is for their career.

John 52:46 But I was like, look, I think I know distributed systems, but I know you do. And this is a very famous professor with big courses on blockchain and hundreds of thousands of people, you know, books on blockchain, all that. And I said, I don’t think that we can scale it. And I don’t think that layers or ZK or any of these things actually solves this for any use case that we’re claiming.

John 53:10 Why am I wrong? If you could show me why I’m wrong, I will, I’ll flip right around because I believe you know what you’re talking about. And they went, no, of course you’re right. But I can’t say that because the dean thinks that we can keep selling more blockchain courses. That was the moment for me.

John 53:32 It’s not just about having coin go up. It’s, you know, I need to sell more courses. We can get people to believe this stuff. You know, crypto was always crypto. But a technological grift I cannot abide. I’m not going to lie to you about my findings in the technological experience. I might be naive. I might not know something yet.

John 53:55 I might be excited about something. I was excited about blockchain for lots of reasons. Most of those reasons are valid. It’s just that we got, I did, all of us, we got solution-y. We said, hey, the solution, here’s my hammer. Where’s your nail? And it turned out that the claims we were making about the technology itself were wrong and easily seeable as wrong, except, boy, there was a lot of money.

John 54:25 There was just a lot of money.

Kevin 54:29 So what do you think about those alternative DLT approaches? Do you think it’s the exact same thing, basically like hashgraphs and these kind of things, or just to get your sentiment on that as well?

John 54:48 Well, going back to The Two But Rule, the question is what are your needs driving your intent? If your intention is to do a hashgraph or something, you really should focus on what needs are you trying to address and then forget about the hashgraph or any other thing, including AI, anything, right? And say what tools are out there to get me across the line on my intentions, right?

John 55:12 And there’s just a lot of big butts that come up and that are hard to overcome if you say I have to do it with thing X. You know, and say, hey, I’m glazing glass, I’m hanging a, I’m hanging glass. Um, here’s a hammer, maybe not the right tool.

Kevin 55:36 That’s really, you know, John, to say that publicly as well. That’s really what I love about our discussions. Because as I said on just our Instagram story as well, you’re really straightforward. You say what you think. And you have this, you know, if I can say this, no bullshit attitude. Like you really think through all that, let’s say, nonsense and focus on what matters, right?

Kevin 56:06 Delivering.

John 56:07 I’ll give you bullshit, but I hopefully, at the, once I realize it’s bullshit, I’ll tell you that it was bullshit. That’s, I’m not immune to bullshit. None of us are. But once I see it plainly, I, I stupidly tend to let people know that I was full of shit. And all we can do is keep our minds open.

Kevin 56:28 Right? Um, I should be as [unclear] as I can be, you know, and I really try to get deep into all these different perspectives and, you know, love that. Thank you for sharing all this.

John 56:48 Well, thank you. I, I love what, you know, you’re so thoughtful on your show and, and, uh, and, and in your work, and, uh, you’re a great leader in my view. Um, and so, uh, keep it up. I love, I love some of the stuff you’ve been posting about the work you’ve been doing with young people. Uh, that’s fantastic.

John 57:05 Uh, try not to get them too into crypto, please. But, you know, the crypto hegemony really needs the next generation to trade goods and services for their bearer bond tokens, uh, maybe, maybe not, but yeah, thanks.

Kevin 57:24 Uh, in either way, uh, thanks John for your time and it was really a pleasure.

John 57:29 Thanks man, it’s good to see you.

Kevin 57:31 This was really a crazy episode. I think Ernesto agrees with me on that. Well, I really love John and I’ve worked with him in the past. And if you see me posting about this no [unclear] approach, building products that make sense, a lot of that I actually learned from John. So I’m really deeply grateful for my work experience with him and even more so that he took the time to talk with me on our podcast today.

Kevin 58:02 And yeah, while of course, I don’t agree with all the things he’s saying about blockchain, but as you heard with a lot of things though, especially when it comes to where blockchain actually makes sense and where it doesn’t, I really, really, really enjoyed this conversation and I maybe even check it out myself again, because I think there are certain hidden nuggets that I maybe during the discussion haven’t even heard myself.

Kevin 58:32 So please let us know what you think about the podcast. Leave a comment below. Hit subscribe, like, whatever. Thank you very much. It really helps our channel. And yeah, definitely check out John’s book. I had the pleasure of checking his free version before it actually came out. So I really can recommend that.

Kevin 58:55 I recommend the book. And yeah, thank you for watching.

58:59 Wavect. The Web3 software company that understands what you want. Are you tired of avoiding hard problems? Do you find yourself trapped in toxic positivity, unable to confront the challenges that lie ahead? Well, The Two But Rule is here to change that. It’s a groundbreaking book that will revolutionize the way you approach problem solving in today’s complex world.

59:24 With a blend of humor and stories from the realms of technology, entrepreneurship and history, The Two But Rule will help you break through avoidance patterns and achieve momentum in everything from changing careers and starting a business to tackling the biggest challenges facing humanity. Whether you’re a business leader, an innovator, a product manager, or a student, The Two But Rule is for anyone seeking to navigate the complexities of our modern world, build things that work, and solve problems without piling a dozen more on top.

59:54 The Two But Rule mixes a serious topic with a healthy dose of adolescent humor that I hope makes you shoot milk out of your nose at least once. Because problem solving should be fun. Join the growing community of readers who have embraced The Two But Rule and witness the positive impact it can have on your personal and professional life.

1:00:14 So what are you waiting for? Get reacquainted with your biggest asset for innovation today by letting The Two But Rule help you turn negative thinking into positive solutions.

Transcribed from the original audio with Whisper large-v3 and AI-reconciled with the original automatic captions. Unclear speech is bracketed; speaker labels and translations are editorial aids. No complete human listening pass. The recording remains authoritative; statements reflect its date. Published June 23, 2024. References to then-current technology, regulation and implementations reflect the conversation’s historical context. Claims about blockchain scalability, transaction costs, comparative security, crypto markets and token classification are Wolpert’s assessments. Stock-based staking for a Mina fork and privacy-preserving coordination are proposed approaches; the Texas usury-law and loan-insurance scenario is hypothetical.

Questions this episode answers

In the episode, Wolpert explains that the rule starts with the first but, as in, but that won’t work, and requires you to follow it with a second but, as in, but it would work if. In his experience running innovation labs and product teams, about five rounds of this is a good recipe for coming up with something innovative, maybe a patent or two. The book is published by Wiley.
Momentum thinking is the term Wolpert uses for the discipline behind the Two But Rule. Instead of letting one objection kill an idea (a one-but culture) or banning objections entirely (a no-buts culture), every objection gets paired with a second but that keeps the idea moving. He observes that forming your second but before speaking can help you pause, remember your point and listen in meetings.
Wolpert criticizes putting sensitive shared data on a blockchain, calling it an anti-pattern and comparing it to a big digital nudist colony. He points to phone number portability as a policy-based solution to lock-in and still sees value in storing hashes and proofs on tamper-resistant public linked lists.
No. In the episode, Wolpert explains that ZK works on regular computers, and putting it on a blockchain stacks one computationally expensive thing on another. Proofs can be stored on a tamper-resistant system, and verifiers can be centralized but observable, for example through continuous state hashing.
He argues the marginal transaction cost on any blockchain is non-zero, while in even the worst banking systems it limits to zero, so a blockchain can never support a global cash use case. He describes Bitcoin instead as digital variable-price bearer bonds for people who, legitimately or otherwise, have a strong need to move large sums across borders with pseudo-impunity and avoidance of tax.

Want this kind of thinking applied to your product?

We build MVPs and act as fractional CTOs for founders who’d rather ship than talk.