Multiple people editing one PowerPoint deck creates chaos: files named "final," lost changes, and no clear master copy. Borrow from software development: use branches for separate edits, merge them back, and treat slides like code. This cuts the redundant versions and speeds up iteration.
we started from scratch and kind of pushed the old systems off the table and started afresh, that we've actually solved some of those core problems that created of the simple issue. I'll point it out to you. And every, every person who's listening or watching has had this problem. If you've ever worked on a PowerPoint with somebody and you have to give a presentation on Monday morning and you sort of say, well, can you add this slide? Somebody has the master sort of presentation. Somebody says, well, put this in as slide 17. And then you come up with a naming schema that says, you know, final, final version as of Sunday at 7:59. And then You know, then you change the name again to really, really final version. And so this whole versioning issue kind of goes out the window. Yeah. And as a result, all the processes downstream become streamlined and allows you to iterate. And taking from the software world, we've created this idea of being able to branch and merge and explore various versions of things. And that whole iterative nature that we talked about from prototyping on the manufacturing side, That's happening in the software side that allows you to explore on a broader basis. And the 2 of them together really can optimize how people build things.
