Embracing Change and Encouraging Disagreement for Better Outcomes | 3min snip from Tom Bilyeu's Impact Theory

Great Wealth Transfer Has Begun: Preparing For A Market Crash & Rising Conflict In 2024 | Ray Dalio

Tom Bilyeu's Impact Theory

CHAPTER

Embracing Change and Encouraging Disagreement for Better Outcomes

This chapter highlights the significance of fostering a culture of change and encouraging diverse opinions to promote innovation. It explores the concept of structured disagreement in organizations and the dual responsibility of individuals and society in effective decision-making.

00:00

Transcript

Play full episode

Transcript

Episode notes

Speaker 3

I don't know the answer to that. At the beginning, of course. Ye, ye,

Speaker 2

ye. Exactly. Like, i mean, i'd start in one big i' just go, you know, ju, start writing code. I mean, then you're coating. Surely there's steps before the oka. Let's pass it to chris. Chris, you write soft were for a living. You're blank canvas coning guy. Now, where do you start? What do you do? I think, because i am who i am, i usually start with a combination

Speaker 1

of writing some sort of document to mix ure i kind of understand what the problem is. Icayou guess, in the beginning, beginning, when some one brings something for me to build, i ask a lot of questions and make sure that it's like, well, are you actually asking me for the thing you want, or you asking me to build the thing you think you need? That's usually where i start. Whenever it's a kind of, actually doesn't mater, doesn't mater, if it's a product person, or if it'something in building for myself, i say like, mi, is the premise that i have assumed here, or someone else has assumed the correct one. And once i kind of figure that out, i'll start with writing up a design dock or a scope do communicate, this is what we're going to build. And then i usually jump into some prototyping. And that's where i start actually, like, throwing some code into a code base. Then, like, the project usually gets legs from there, and we kind of e know if it's something for work. We develop out that design dock more we start having discussions than we actually make the four real code base, which might, unfortunately, be taking that prototype code i built, or it might be starting from fresh, which is, dely a preferable thing tos. Prototype code is never really written as well as we'd like it to be. That's usually like the the on ramp that i take. But that's really a lot. Because i'm a writer, so my comfort zone is like an empty document in google doxes or an empty vim window where i can just start typing out, o what is it that i'm trying to do? Blank

Speaker 2

canvas. Johnny, does it resinate with you? Is that similar to your process? Ye,

Speaker 3

i' say so.

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.