Podcasts about iterative design

How do you turn 5,127 failures into a multi-billion-dollar empire? James Dyson turned dust into possibility, failure into discovery, and frustration into revolution.     Dyson didn't just build a better vacuum; he redefined a whole industry. Facing thousands of failed prototypes, crushing financial setbacks, and a dismissive industry that insisted a superior vacuum was impossible, Dyson transformed doubt into fuel that created an empire he still owns and operates today. Dyson's genius stretched far beyond engineering. He was a contrarian thinker whose natural state was to defy the experts. From reinventing hand dryers to fans and hairdryers, Dyson repeatedly turned mundane frustrations into game-changing products. His relentless curiosity and willingness to fail publicly set new standards for innovation. When competitors mocked him, he stayed focused. When patents were threatened, he defended fiercely. Dyson's story is one of unwavering persistence, unorthodox creativity, and the courage to trust his own instincts—even when everyone else doubted.      This is the story of James Dyson. Learn how one decision can change everything for a whole family.    This episode is for informational purposes only and is based on Against the Odds: An Autobiography by James Dyson. Quotes from Against the Odds and James Dyson's Invention: A Life  (02:35) Prologue: The Kitchen Floor Experiment PART 1 - EARLY SPARKS OF TENACITY (05:05) A Childhood of Resilience and Determination (08:19) Gresham's School (11:25) From Art to Engineering: A Defiance of Convention (14:58) A Mentor: Jeremy Fry (17:37) Just Build It (19:23) The Sea Truck (22:16) Lessons From The Egyptians (24:16) Misfit Mentality PART 2: FIRST INVENTIONS AND HARD LESSONS (26:48) Reinventing The Wheel(barrow) (28:54) Popular Not Profitable (30:56) Leaving Ballbarrow with Nothing (34:09) History of the Vaccuum (36:23) Cyclone in a Sawmill (39:17) 5,127 Prototypes (41:57) Industry Rejection (44:14) Building the Business PART 3: BUILDING AN EMPIRE (48:15) Passion Over Profit (50:04) Beyond Vacuums (53:08) R&D Culture & Iterative Design (55:44) Patent Wars & Legal Battles (57:49) Value of Keeping Ownership (59:59) Recap of Dyson's Journey (01:02:55) SHANE'S REFLECTIONS Upgrade — If you want to hear my thoughts and reflections at the end of all episodes, join our membership: ⁠⁠⁠⁠⁠⁠⁠fs.blog/membership⁠⁠ and get your own private feed. Newsletter - The Brain Food newsletter delivers actionable insights and thoughtful ideas every Sunday. It takes 5 minutes to read, and it's completely free. Learn more and sign up at fs.blog/newsletter Learn more about your ad choices. Visit megaphone.fm/adchoices

https://www.linkedin.com/in/antondeweger/

In this episode of the Sneaker History Podcast, host Nick Engvall speaks with Charlie Hudak and Tyler Pinkos, the creators behind the new Sun Day Red shoes designed for Tiger Woods. They discuss their backgrounds in footwear design, the intense development process, and the unique challenges of creating a high-performance golf shoe for one of the greatest athletes of all time. The conversation delves into the iterative design process, the importance of fit and comfort, and the storytelling elements embedded in the shoe's design. In this conversation, Charley Hudak, Sr. Creative Director of Footwear, and Tyler Pinkos, Head of Footwear Development and Sourcing, discuss their collaboration with Tiger Woods on the design of the Sun Day Red Pioneer Cyprus golf shoe. They explore the innovative elements of the shoe, the storytelling behind its design, and the influence of Tiger Woods on the golf community and culture. The discussion highlights the importance of performance in footwear design, the future of golf shoes, and the personal passion both designers have for the game of golf.

After a behind-the-scenes tour of their shot shell manufacturing facility in East Alton, Illinois, Dr. Mike Brasher sits down with Nate Robinson, Ben Frank, and Grant Jeremiah from Winchester Ammunition to discuss how a long-standing passion for waterfowl hunting has helped Winchester become the most trusted name in waterfowl ammunition. From Dry-Lok to Blindside and new waterfowl loads such as Bismuth and Last Call TSS, the group discusses the innovation behind these products, their commitment to quality, and the design and testing that makes them the best in the business: Winchester Ammunition – the official ammunition of Ducks Unlimited and our proud partner in conservation.Listen now: www.ducks.org/DUPodcastSend feedback: DUPodcast@ducks.org

Our guest is Yasemin Cenberoglu, who was the first designer to work on Microsoft's Copilot, all in secret, before the world was exposed to ChatGPT for the first time.Yasemin is a Principal Design Manager at Microsoft, leading the Copilot product for Teams Meetings, Calling, and Devices. She's the first designer to shape what Copilot is today. Previously, she served as the Director of Design at Digitalist. Yasemin is an advisory board member at IDEA School of Design at Capilano University. She studied in Germany and then at Cal State, in the Bay area.00:49 Yasmin's Background and Role 02:09 Design Differences: Europe vs North America 03:44 Service Design Methodologies 03:58 Co-Creating with OpenAI 04:38 Blueprints and Customer Journeys 05:27 Rapid Prototyping and Testing 06:20 Reconnecting with Yasmin 07:06 The Excitement of Innovation 10:04 Defining Value Drivers 11:50 Building High-Level Scenarios 12:49 Managing Feasibility and Vision 15:53 Lessons Learned from GenAI 21:05 Testing and User Feedback 22:51 Iterative Design and AI 31:52 Building Trust in AI 34:12 Service Design in AI 39:11 Deciding Between Co-Pilot, Agent, or Chatbot 43:41 Future of Assistive Software 47:27 Advice for Aspiring AI DesignersEpisode is hosted by:Arpy Dragffy Guerrero (Founder & Head of product strategy, PH1 Research) https://www.linkedin.com/in/adragffy/ Brittany Hobbs (VP Insights, Huge) https://www.linkedin.com/in/brittanyhobbs/Thank you for listening to the Design of AI podcast. We interview leaders and practitioners at the forefront of AI. If you like this episode please remember to leave a rating and to follow us on your favorite podcast app.Take part in the conversations about AI https://www.linkedin.com/company/designofai/ This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit designofai.substack.com

Ask yourself a very honest question: is what I'm doing working?Is my training, my nutrition, all the things actually giving me the physique that I want, whether that's being lean and muscular or big and strong?If you're like most people, you start with initial excitement and motivation, followed by hitting one roadblock after another, not quite getting what you want, eventually giving up and then hopping to the next thing.Learn about the engineering concept of iterative design and how it can help you constantly improve and overcome the plateaus and roadblocks common to physique development.Learn how to apply this systematic, data-driven method to your fitness journey to set realistic, measurable goals for your physique, create and refine your training and nutrition plans, use data to make informed decisions about your progress, and overcome plateaus and setbacks.We walk through a real-world example of how to apply iterative design to lose fat and gain muscle.Book a FREE 15-minute Rapid Nutrition Assessment, designed to fine-tune your strategy, identify your #1 roadblock, and give you a personalized 3-step action plan in a fast-paced 15 minutes. Main Takeaways:Iterative design is a powerful tool for long-term physique transformation that transforms setbacks into valuable data points for continuous improvementThe six phases: design, implement, test, evaluate, refine, and repeatThis approach leads to sustainable results by adapting to your body's changing needs

In this episode of Passion Struck, host John R. Miles interviews Noam Platt, the founder of MakeGood, an organization dedicated to revolutionizing the lives of individuals with disabilities through assistive design. The discussion highlights the power of open-source design and 3D printing in making assistive technology more accessible and affordable. Noam's collaborations with Tulane University and LSU have not only accelerated the production of assistive technologies but also provided students with hands-on experience in making a difference in their communities. The episode showcases heartwarming stories of children benefiting from customized mobility trainers, demonstrating the life-changing impact of assistive technology. Through partnerships and community engagement, Noam and his team are empowering individuals with disabilities and inspiring others to contribute to the field of assistive technology.Order a copy of my book, "Passion Struck: Twelve Powerful Principles to Unlock Your Purpose and Ignite Your Most Intentional Life," today! This book, a 2024 must-read chosen by the Next Big Idea Club, has garnered multiple accolades, including the Business Minds Best Book Award, the Eric Hoffer Award, and the Non-Fiction Book Awards Gold Medal. Don't miss out on the opportunity to transform your life with these powerful principles!Full show notes and resources can be found here:  https://passionstruck.com/noam-platt-inclusive-innovation-change-the-world/In this episode, you will learn:The need for affordable assistive technologyThe role of open-source design in democratizing assistive technologyCollaborative design approach and international partnershipsPartnerships with Tulane and LSU in accelerating assistive technology useStories of students making a difference through assistive technologyTestimonials of the life-changing impact of toddler mobility trainers, such as Sebastian's storyAll things Noam Platt: https://makegood.design/SponsorsBrought to you by Clariton, fast and powerful relief is just a quick trip away. Ask for Claritin-D at your local pharmacy counter. You don't even need a prescription! Go to “CLARITIN DOT COM” right now for a discount so you can Live Claritin Clear.--► For information about advertisers and promo codes, go to:https://passionstruck.com/deals/Catch More of Passion StruckCan't miss my episode with Hari Budha Magar on Defy Your Limits to Conquer Your EverestListen to my interview with Jen Bricker-Bauer On Everything is PossibleWatch my episode with Staff Sergeant Travis Mills on How You Bounce Back and Rise Above AdversityListen to my solo episode on 7 Reasons Why Acts of Kindness Are More than Meets the EyeLike this show? Please leave us a review here-- even one sentence helps! Consider including your Twitter or Instagram handle so we can thank you personally!Show LessTranscriptComing up next on passion struck.We don't control what our politicians do. We don't control where the culture is going. We don't control what our neighbors do. We don't control what other bu...

Welcome back to The Bilna Sandeep Show! Today's episode features two amazing guests, Gulnar and Gafoor, co-founders of PACI and other ventures. Join us as we delve into their journey and discuss the innovative approach PACI takes towards accounting and finance. Check out this episode on YouTube  Part 1: ⁠⁠https://youtu.be/az1KVicwF60 Part 2: https://youtu.be/sOZLbYxg2QM Timestamps for your convenience 00:00 - Introduction and Guest Welcome 02:16 - PACI's Approach and Simplifying Processes 04:20 - Tech-Oriented Approach and Introduction to AI in Accounting 06:12 - Understanding Customer Behavior and Evolution of Services 08:57 - Focus on Micro and Small Businesses 17:05 - Continuous Improvement and Customer-Centric Approach 21:23 - Insights and Challenges in Business Operations 28:06 - Entrepreneurship Approaches 30:00 - Enhancing Customer Experience 35:00 - Iterative Design and Feedback Integration 40:00 - Marketing Messages and Conversion Rates 45:00 - Decision-Making in Marketing 50:00 - Observing Customer Behavior for Insights 55:00 - Closing Remarks and Final Thoughts 1:00:00 - Final Takeaways and Sales Pitch If you want to join my network of amazing people, book a call with me at this⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠link⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠: ⁠⁠https://calendly.com/bilnasandeep ⁠⁠ Gulnar's Linkedin: https://www.linkedin.com/in/gulnar-basheer-b936bb13b/ Gafoor's Linkedin: https://www.linkedin.com/in/agf1/ PACI's Website: https://paci.ai/ Homepreneurs Club Instagram: ⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/homepreneursclub/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Growwie's Instagram:⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/growwiemedia/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Growwie's Website:⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠www.growwie.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Built Market Lab's Website:⁠ ⁠⁠⁠⁠⁠www.builtmarketlab.com⁠⁠⁠⁠⁠⁠ If you found this episode useful, I would be grateful if you could take a screenshot and share it on Instagram stories by tagging me. If you are listening to this Podcast on iTunes, please take a moment to rate my podcast. I would really appreciate your feedback, and it will help me do more for you all. Select 'View in iTunes' > click on 'Ratings and Reviews' > You can tap on the number of stars to rate and click and write a review to type your valuable feedback for me. Rate us on iTunes and leave us a review on today's episode. Be sure to let me know what valuable insights you gained from today's episode. Follow us on social media for more tips: Bilna's Instagram -⁠⁠ ⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/bilnasandeep/⁠⁠⁠⁠⁠⁠⁠⁠⁠ Homepreneurs Instagram -⁠⁠ ⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/homepreneurs/⁠⁠⁠⁠⁠⁠⁠⁠⁠ Website -⁠⁠ ⁠⁠⁠⁠⁠⁠⁠https://bilnasandeep.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.homepreneursclub.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠ Facebook -⁠⁠ ⁠⁠⁠⁠⁠⁠⁠https://www.facebook.com/homepreneursclub/⁠⁠⁠⁠⁠⁠⁠⁠⁠ YouTube -⁠⁠ ⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/c/BilnaSandeep/featured⁠⁠⁠⁠⁠⁠⁠⁠⁠ Send in a voice message: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://anchor.fm/bilnasandeep/message⁠⁠⁠⁠⁠ --- Send in a voice message: https://podcasters.spotify.com/pod/show/bilnasandeep/message

In this insightful conversation between Dwayne Paisley-Marshall and Mourad Bahrouch, the duo delves deep into the realm of augmented reality (AR), virtual reality (VR), and the rapid pace of technological advancement. They explore how these innovations are reshaping industries, challenging traditional approaches, and opening up new possibilities for human interaction with technology. From discussing the potential of AR in real estate to pondering the implications of storytelling in embracing change, this dialogue offers a thought-provoking exploration of the evolving relationship between humanity and technology. https://www.digitalmatter.studio/ https://www.creativetechnologists.nl/ (00:00) Dwayne Paisley-Marshall (07:00) AR in Real Estate, New Opportunities (13:00) The Evolution of the iPhone and Iterative Design (19:00) AR Tours: Enhancing Travel Experiences (21:00) The Future of AI and Humor-Centered Design (24:00) The Importance of Authenticity in Branding Amidst Technological Change --- Send in a voice message: https://podcasters.spotify.com/pod/show/mountain-collective/message

Spatial Computing is here… with 2D apps and some 3D movies I don't wanna see again? Give it time, haters! When iPhone hit, we didn't need until social media apps. iPads hit because of SkyWalk app… VisionPro developer APIs are out and available, so get busy y'all! Meanwhile, Gary Gensler is on anti-AI train again: thinks GPTs create false layers of regulatory truth. Bitcoin touched $50,000, a great sign for ETH and all alt-coins, but will sustain through halvening? And Wolrdcoin just became eSports Verification Orb, just in time for the 2024 EA Madden Games. Join us as we unpack and repack it all! Chapters: 00:00 Introduction and Screen Time 00:27 Discussion on Apple Vision Pro 02:18 Spatial Computing and Immersive Experiences 03:36 3D Movies and Apps on Apple Vision Pro 04:06 Challenges and Limitations of Apple Vision Pro 06:02 Gaming and Immersive Environments 07:46 Isolating Nature of Apple Vision Pro 08:44 Shared Experiences and Social Component 09:15 Timing and Use Cases of Apple Vision Pro 10:14 Themed Environments and Immersive Rooms 11:13 User Experience Challenges with Apple Vision Pro 12:39 Interaction and Navigation in Apple Vision Pro 14:06 Sharing and Privacy Concerns 15:33 Limitations of Sharing Apple Vision Pro 16:09 Future Iterations and User Feedback 17:04 Design Decisions and Iterative Progress 18:33 Transition to Must-Have Product 20:02 Low-Cost Alternatives to Apple Vision Pro 22:26 Spatial Video and Content Creation 23:55 Blended Reality and Clear Glasses 25:28 Augmented Reality and Social Interaction 27:44 Cryptocurrency and Microtransactions 29:22 Transitionary Period and Hardware Considerations 30:48 Social Media, Betting, and Cryptos 32:07 Conspiracy Theories and Super Bowl 34:56 Twitter, Jay-Z, and Spatial Computing 36:41 Rigged Super Bowl and Cryptocurrency 37:39 Biden's Laser Eyes and Market Trends 38:48 Killer Apps in Web 3 41:01 Esports and Identity Verification Apple Vision Pro, Augmented Reality, Immersive Tech, Digital Interactions, Digital Persona, Starwalk App, Virtual Reality, VR, Isolation, Technology Interaction, Cryptocurrency, Bitcoin ETFs, Killer Apps, Esports, Blockchain, Content Creation, Social Engagement, Spatial Computing, 3D Movies, iPhone, iPad, Metaverse, Hardware and Software Integration, Digital Presence, Worldcoin Project, Thematic Digital Landscapes, Personal Stories, Nascent Technology, Cinematic Wonder, Iron Throne Room, Game of Thrones, COVID-19 Lockdowns, Familiar Yet Visually Obscured Setting, Iterative Design, iPhone 15, Camera Settings, Low-Cost Alternatives, Budget-Friendly Devices, First-Person Content Creation, Smart Glasses, Digital Landscape, Digital Identities, Metaverse, Xbox, Halo, Worldcoin Project, Hardware and Software Integration, Digital Presence, Blockchain, Ownership, Identity

Happy 2024! We appreciated all the feedback on the listener survey (still open, link here)! Surprising to see that some people's favorite episodes were others' least, but we'll always work on improving our audio quality and booking great guests. Help us out by leaving reviews on Twitter, YouTube, and Apple Podcasts!

British Cycling story sourced from here If you want to support on⁠⁠⁠ Patreon⁠⁠⁠ I'd appreciate it. If you have any questions or want to submit a story email questions@workshoptherapypodcast.com If you are considering therapy please consider checking out Betterhelp.com through this affiliate link where you will get a free week with your initial subscription. Check out the social medias ⁠⁠⁠⁠Instagram⁠⁠⁠⁠ ⁠⁠⁠⁠Facebook⁠⁠⁠⁠ ⁠⁠⁠⁠TikTok⁠⁠⁠⁠ ⁠⁠⁠⁠YouTube --- Send in a voice message: https://podcasters.spotify.com/pod/show/workshoptherapy/message

This week we welcome back Dr. Scott Bland! Host: Cale Matthews   Audio Engineer: Art Pipok Visit us at ⁠⁠⁠⁠⁠⁠⁠⁠⁠solid7podcast.com⁠⁠⁠⁠⁠⁠⁠⁠⁠ to snag some ⁠⁠⁠⁠⁠⁠⁠⁠⁠merch⁠⁠⁠⁠⁠⁠⁠⁠⁠, rate the show, ⁠⁠⁠⁠⁠⁠⁠⁠⁠buy us a Jocko Go⁠⁠⁠⁠⁠⁠⁠⁠⁠, see upcoming events, follow us on social media, support worthy causes, and become a ⁠⁠⁠⁠⁠⁠⁠⁠⁠Patreon⁠⁠⁠⁠⁠⁠⁠⁠⁠ supporter. © Copyright 2023 Solid Seven Podcast. All Rights Reserved.

Kyle Dumont spent many years as a hardware developer for iRobot, then got a Masters of Science and an MBA dual degree at Harvard, then spun out AllSpice which is a software platform for managing electronic engineering feedback and revision tracking amongst other things. Today Kyle is going to share some valuable knowledge for inventors, startups, and small manufacturers on what iterative hardware product development is between manufacturing runs, who the feedback loop stakeholders are, and how to collect, organize, prioritize, and execute on that iterative feedback information to ensure the best improvements to your physical consumer product design. Today you will hear us talk about: What iterative design in hardware is between manufacturing runs Legacy design is based on a waterfall model of design Software has done a great job of iterating very quickly. Get designs in the hands of engineers, or even better, users. Iterative design can sometimes be forced on you if you need to make changes, so better to have the processes Who are the stakeholders: Customers, the most important stakeholders (both current and potential customers) Cost reduction Engineering design, multiple different disciplines (hardware, software, firmware, PCB, visual, industrial design, etc.) Procurement, product managers, Manufacturers Get hardware product engineers in front of customers What tools can be used to collect, organize, prioritize, and implement Version control is a great way to organize version control / revision control.  This is the foundation. Start to consider comparing versions. Do you have the channels and tools to be able to have the various product stakeholders to provide input on the product. Integrating tools together so that the most information Avoid silos of different departments, ideally, you have all information together. Use priority flagging to tag the importance of issues or opportunities. EPISODE LINKS: Kyle Dumont Links: LinkedIn | AllSpice The Product Startup Podcast Links: https://www.ProductStartup.com/ Instagram | LinkedIn | Facebook Page | Facebook Group | Pinterest | Twitter | YouTube PTC Links: https://www.ptc.com/ OnShape | Creo Mako Design Links: https://www.makodesign.com/ YouTube | Instagram | LinkedIn | Facebook | Pinterest | Twitter Kevin Mako Links: Instagram | LinkedIn | Quora | Facebook | Twitter Partner: PTC's best-in-class software solutions Onshape: The only cloud-native product development platform that delivers full-featured computer-aided design (CAD), integrated product data management (PDM) and enterprise analytics in a single system, and Creo: 3D CAD solution that provides designers with the most innovative tools to build better products faster, such as generative design, additive manufacturing, real-time simulation, IIoT, and augmented reality. Producer: MAKO Design + Invent is the original firm providing world-class consumer product development services tailored to startups, small manufacturers, and inventors. Simply put, we are the leading one-stop-shop for developing your physical product from idea to store shelves, all in a high-quality, cost-effective, and timely manner. We operate as one powerhouse 30-person product design team spread across 4 offices to serve you (Austin, Miami, San Francisco, & Toronto). We have full-stack in-house industrial design, mechanical engineering, electrical engineering, patent referral, prototyping, and manufacturing services. To assist our startup and inventor clients, in addition to above, we help with business strategy, product strategy, marketing, and sales/distribution for all consumer product categories. Learn more about your ad choices. Visit megaphone.fm/adchoices

Traditional design is slower and more expensive. IDC is faster and more efficient.

https://www.lesswrong.com/posts/xFotXGEotcKouifky/worlds-where-iterative-design-failsCrossposted from the AI Alignment Forum. May contain more technical jargon than usual.In most technical fields, we try designs, see what goes wrong, and iterate until it works. That's the core iterative design loop. Humans are good at iterative design, and it works well in most fields in practice.In worlds where AI alignment can be handled by iterative design, we probably survive. So long as we can see the problems and iterate on them, we can probably fix them, or at least avoid making them worse.By the same reasoning: worlds where AI kills us are generally worlds where, for one reason or another, the iterative design loop fails. So, if we want to reduce X-risk, we generally need to focus on worlds where the iterative design loop fails for some reason; in worlds where it doesn't fail, we probably don't die anyway.Why might the iterative design loop fail? Most readers probably know of two widely-discussed reasons:Fast takeoff: there will be a sudden phase shift in capabilities, and the design of whatever system first undergoes that phase shift needs to be right on the first try.Deceptive inner misalignment: an inner agent behaves well in order to deceive us, so we can't tell there's a problem just by trying stuff and looking at the system's behavior.… but these certainly aren't the only reasons the iterative design loop potentially fails. This post will mostly talk about some particularly simple and robust failure modes, but I'd encourage you to think on your own about others. These are the things which kill us; they're worth thinking about.Crossposted from the AI Alignment Forum. May contain more technical jargon than usual.In most technical fields, we try designs, see what goes wrong, and iterate until it works. That's the core iterative design loop. Humans are good at iterative design, and it works well in most fields in practice.In worlds where AI alignment can be handled by iterative design, we probably survive. So long as we can see the problems and iterate on them, we can probably fix them, or at least avoid making them worse.By the same reasoning: worlds where AI kills us are generally worlds where, for one reason or another, the iterative design loop fails. So, if we want to reduce X-risk, we generally need to focus on worlds where the iterative design loop fails for some reason; in worlds where it doesn't fail, we probably don't die anyway.Why might the iterative design loop fail? Most readers probably know of two widely-discussed reasons:Fast takeoff: there will be a sudden phase shift in capabilities, and the design of whatever system first undergoes that phase shift needs to be right on the first try.Deceptive inner misalignment: an inner agent behaves well in order to deceive us, so we can't tell there's a problem just by trying stuff and looking at the system's behavior.… but these certainly aren't the only reasons the iterative design loop potentially fails. This post will mostly talk about some particularly simple and robust failure modes, but I'd encourage you to think on your own about others. These are the things which kill us; they're worth thinking about.

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: Worlds Where Iterative Design Fails, published by johnswentworth on August 30, 2022 on The AI Alignment Forum. In most technical fields, we try designs, see what goes wrong, and iterate until it works. That's the core iterative design loop. Humans are good at iterative design, and it works well in most fields in practice. In worlds where AI alignment can be handled by iterative design, we probably survive. So long as we can see the problems and iterate on them, we can probably fix them, or at least avoid making them worse. By the same reasoning: worlds where AI kills us are generally worlds where, for one reason or another, the iterative design loop fails. So, if we want to reduce X-risk, we generally need to focus on worlds where the iterative design loop fails for some reason; in worlds where it doesn't fail, we probably don't die anyway. Why might the iterative design loop fail? Most readers probably know of two widely-discussed reasons: Fast takeoff: there will be a sudden phase shift in capabilities, and the design of whatever system first undergoes that phase shift needs to be right on the first try. Deceptive inner misalignment: an inner agent behaves well in order to deceive us, so we can't tell there's a problem just by trying stuff and looking at the system's behavior. . but these certainly aren't the only reasons the iterative design loop potentially fails. This post will mostly talk about some particularly simple and robust failure modes, but I'd encourage you to think on your own about others. These are the things which kill us; they're worth thinking about. Basics: Hiding Problems Example/Analogy: The Software Executive Imagine that a software company executive, concerned about the many errors coming from the software, creates a new incentive scheme: software developers get a monetary reward for changes which decrease the rate of error messages showing up on the manager's dashboard, and get docked for changes which increase the rate of error messages. As Tyler Cowen would say: “solve for the equilibrium”. Obvious equilibrium here: the developers stop throwing error messages when they detect a problem, and instead the software just fails silently. The customer's experience remains the same, but the manager's dashboard shows fewer error messages. Over time, the customer's experience probably degrades, as more and more problems go undetected. In the short run, the strategy may eliminate some problems, but in the long run it breaks the iterative design loop: problems are not seen, and therefore not iterated upon. The loop fails at the “see what goes wrong” step. Why RLHF Is Uniquely Terrible The software executive's strategy is the same basic idea as Reinforcement Learning from Human Feedback (RLHF). AI does something, a human looks at what happened to see if it looks good/bad, and the AI is trained on the human's feedback. Just like the software executive's anti-error-message compensation scheme, RLHF will probably result in some problems actually being fixed in the short term. But it renders the remaining problems far less visible, and therefore breaks the iterative design loop. In the context of AI, RLHF makes it far more likely that a future catastrophic error will have no warning signs, that overseers will have no idea that there's any problem at all until it's much too late. Note that this issue applies even at low capability levels! Humans overlook problems all the time, some of those mistakes are systematic, and RLHF will select for places where humans systematically overlook problems; that selection pressure applies even when the neural net lacks great capabilities. This is the core reason why I consider RLHF uniquely terrible, among alignment schemes. It is the only strategy I know of which actively breaks the iterative design loop; it makes probl...

Link to original articleWelcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: Worlds Where Iterative Design Fails, published by johnswentworth on August 30, 2022 on The AI Alignment Forum. In most technical fields, we try designs, see what goes wrong, and iterate until it works. That's the core iterative design loop. Humans are good at iterative design, and it works well in most fields in practice. In worlds where AI alignment can be handled by iterative design, we probably survive. So long as we can see the problems and iterate on them, we can probably fix them, or at least avoid making them worse. By the same reasoning: worlds where AI kills us are generally worlds where, for one reason or another, the iterative design loop fails. So, if we want to reduce X-risk, we generally need to focus on worlds where the iterative design loop fails for some reason; in worlds where it doesn't fail, we probably don't die anyway. Why might the iterative design loop fail? Most readers probably know of two widely-discussed reasons: Fast takeoff: there will be a sudden phase shift in capabilities, and the design of whatever system first undergoes that phase shift needs to be right on the first try. Deceptive inner misalignment: an inner agent behaves well in order to deceive us, so we can't tell there's a problem just by trying stuff and looking at the system's behavior. . but these certainly aren't the only reasons the iterative design loop potentially fails. This post will mostly talk about some particularly simple and robust failure modes, but I'd encourage you to think on your own about others. These are the things which kill us; they're worth thinking about. Basics: Hiding Problems Example/Analogy: The Software Executive Imagine that a software company executive, concerned about the many errors coming from the software, creates a new incentive scheme: software developers get a monetary reward for changes which decrease the rate of error messages showing up on the manager's dashboard, and get docked for changes which increase the rate of error messages. As Tyler Cowen would say: “solve for the equilibrium”. Obvious equilibrium here: the developers stop throwing error messages when they detect a problem, and instead the software just fails silently. The customer's experience remains the same, but the manager's dashboard shows fewer error messages. Over time, the customer's experience probably degrades, as more and more problems go undetected. In the short run, the strategy may eliminate some problems, but in the long run it breaks the iterative design loop: problems are not seen, and therefore not iterated upon. The loop fails at the “see what goes wrong” step. Why RLHF Is Uniquely Terrible The software executive's strategy is the same basic idea as Reinforcement Learning from Human Feedback (RLHF). AI does something, a human looks at what happened to see if it looks good/bad, and the AI is trained on the human's feedback. Just like the software executive's anti-error-message compensation scheme, RLHF will probably result in some problems actually being fixed in the short term. But it renders the remaining problems far less visible, and therefore breaks the iterative design loop. In the context of AI, RLHF makes it far more likely that a future catastrophic error will have no warning signs, that overseers will have no idea that there's any problem at all until it's much too late. Note that this issue applies even at low capability levels! Humans overlook problems all the time, some of those mistakes are systematic, and RLHF will select for places where humans systematically overlook problems; that selection pressure applies even when the neural net lacks great capabilities. This is the core reason why I consider RLHF uniquely terrible, among alignment schemes. It is the only strategy I know of which actively breaks the iterative design loop; it makes probl...

All too often what some PO's and teams call an "Iteration", is anything but. Seeing that far too often, this episode explores some of the reasons why and ways to iterate with our teams, products, practices, and selves. Got any tips or tricks to make sure that you are iterating towards success? Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com Links: PO Coaching and Consulting - seek taiju SmartSheet - The Power of Iterative Design and Process  Jeff Patton - Don't Know What I Want, But I Know How to Get It  Troubleshooting Agile Podcast - https://agileconversations.com/troubleshooting-agile-podcast/ Jens-Fabian Goetzmann - The Iteration Imperative  Rich Mironov - Selling Problems (and Then Solutions) Instead of Philosophy Jens-Fabian Goetzmann - Product Teardowns at Yammer 

In the 21st century, iterative design is the name of the game. Long gone are the days of traditional product development, where teams would have a product idea, build it, and then put it out into the world in the hopes it would sell. Product teams now build and adapt their plans based on user data, feedback, and recommendations. This means the development cycle for a product today is a series of little feedback loops. Each loop adds value, features, and removes errors to a constantly evolving product. We use this style of development at Passion.io and we encourage our experts to do the same. We like to use a pancake as an example. When you're making pancakes the first one you flip is always a bit dodgy. It might not flip properly or get a bit burned, but that is ok, because you'll improve your pancake making process for the second pancake. The same principle applies to building anything. Get a working product, get feedback and data, then use that to improve it! It's what PassionFighter Keith Kern did with his second cohort of clients. After successfully taking his first group of students through their 6-week challenge he used the data and feedback he gathered from that process to improve his product moving forward. Signup for our free training here: https://passion.io/scale Guest Profile Keith Kern is a California based PassionFighter who has built the app, Build Your Power (BYP). He is currently taking his second cohort of students through his 6-week challenge.

We want early feedback to inform foundational or load-bearing decision making before committing to hard/expensive to change design decisions. But we don’t want to start building based on flawed design decisions, the consequences of which are hard/expensive to change when we discover it is faulty. The problem is, how do we balance these two polarities from an either-or to both-and thinking. In this session, we will explore contexts and tradeoffs in upfront design versus iterative design. Joining us to share their perspectives and experiences in a never-ending discussion are: *Dawn Ahukanna (Design Principal and Front-End Architect) *Rebecca Wirfs-Brock (Architecture, Design Heuristics, and Agile Practices) *Diana Montalion (Architecting content systems strategies for enterprise) *Vladik Khononov (Software Engineer and Cloud Architect) and *Trond Hjorteland (IT Architect and aspiring sociotechnical systems designer). We will facilitate using a polarity map from Barry Johnson to guide the conversation and find out the patterns and signs to observe to start managing these polarities for yourselves.

This week in ‘PPP30: 7 Patterns for Highly Efficient Project Managers' I put my $.02 on the concepts from Stephen R. Covey's great work, but with emphasis on being efficient Project Managers. The "7 Patterns": Take Ownership Plan Ahead, But be Flexible Identify Issues and Set Objectives Don't Let Perfect be the Enemy of Good Consider the O.O.D.A Loop Develop the Team's Operational Tempo Iteratively Design Yourself Episode References: “Effective and efficient both mean "capable of producing a result," from How to Use Effective and Efficient at https://learnersdictionary.com/qa/How-to-Use-Effective-and-Efficient#:~:text=The%20words%20effective%20and%20efficient,%2C%20time%2C%20or%20energy%22. From Merriam-Webster: Effective: producing a decided, decisive, or desired effect Efficient: capable of producing desired results with little or no waste (as of time or materials) “A focus on disciplines, activities, technologies and resources that gives organizational leaders the mechanisms and controls they need to understand how to enable consistent and repeatable organizational change in response to changing patterns.” from Pattern-Based Approaches for Organizations' Agility at https://www.igi-global.com/dictionary/operational-tempo/40065 “You can think of the iterative design process as a continuous cycle of prototyping, testing, and making adjustments and refinements.” from What is Iterative Design? (and Why You Should Use It) at https://www.enginess.io/insights/what-is-iterative-design

This week in ‘PPP30: 7 Patterns for Highly Efficient Project Managers' I put my $.02 on the concepts from Stephen R. Covey's great work, but with emphasis on being efficient Project Managers. The "7 Patterns": Take Ownership Plan Ahead, But be Flexible Identify Issues and Set Objectives Don't Let Perfect be the Enemy of Good Consider the O.O.D.A Loop Develop the Team's Operational Tempo Iteratively Design Yourself Episode References: “Effective and efficient both mean "capable of producing a result," from How to Use Effective and Efficient at https://learnersdictionary.com/qa/How-to-Use-Effective-and-Efficient#:~:text=The%20words%20effective%20and%20efficient,%2C%20time%2C%20or%20energy%22. From Merriam-Webster: Effective: producing a decided, decisive, or desired effect Efficient: capable of producing desired results with little or no waste (as of time or materials) “A focus on disciplines, activities, technologies and resources that gives organizational leaders the mechanisms and controls they need to understand how to enable consistent and repeatable organizational change in response to changing patterns.” from Pattern-Based Approaches for Organizations' Agility at https://www.igi-global.com/dictionary/operational-tempo/40065 “You can think of the iterative design process as a continuous cycle of prototyping, testing, and making adjustments and refinements.” from What is Iterative Design? (and Why You Should Use It) at https://www.enginess.io/insights/what-is-iterative-design

This week in ‘PPP30: 7 Patterns for Highly Efficient Project Managers’ I put my $.02 on the concepts from Stephen R. Covey’s great work, but with emphasis on being efficient Project Managers. The "7 Patterns": Take Ownership Plan Ahead, But be Flexible Identify Issues and Set Objectives Don’t Let Perfect be the Enemy of Good Consider the O.O.D.A Loop Develop the Team’s Operational Tempo Iteratively Design Yourself Episode References: “Effective and efficient both mean "capable of producing a result," from How to Use Effective and Efficient at https://learnersdictionary.com/qa/How-to-Use-Effective-and-Efficient#:~:text=The%20words%20effective%20and%20efficient,%2C%20time%2C%20or%20energy%22. From Merriam-Webster: Effective: producing a decided, decisive, or desired effect Efficient: capable of producing desired results with little or no waste (as of time or materials) “A focus on disciplines, activities, technologies and resources that gives organizational leaders the mechanisms and controls they need to understand how to enable consistent and repeatable organizational change in response to changing patterns.” from Pattern-Based Approaches for Organizations' Agility at https://www.igi-global.com/dictionary/operational-tempo/40065 “You can think of the iterative design process as a continuous cycle of prototyping, testing, and making adjustments and refinements.” from What is Iterative Design? (and Why You Should Use It) at https://www.enginess.io/insights/what-is-iterative-design

This week in ‘PPP30: 7 Patterns for Highly Efficient Project Managers’ I put my $.02 on the concepts from Stephen R. Covey’s great work, but with emphasis on being efficient Project Managers. The "7 Patterns": Take Ownership Plan Ahead, But be Flexible Identify Issues and Set Objectives Don’t Let Perfect be the Enemy of Good Consider the O.O.D.A Loop Develop the Team’s Operational Tempo Iteratively Design Yourself Episode References: “Effective and efficient both mean "capable of producing a result," from How to Use Effective and Efficient at https://learnersdictionary.com/qa/How-to-Use-Effective-and-Efficient#:~:text=The%20words%20effective%20and%20efficient,%2C%20time%2C%20or%20energy%22. From Merriam-Webster: Effective: producing a decided, decisive, or desired effect Efficient: capable of producing desired results with little or no waste (as of time or materials) “A focus on disciplines, activities, technologies and resources that gives organizational leaders the mechanisms and controls they need to understand how to enable consistent and repeatable organizational change in response to changing patterns.” from Pattern-Based Approaches for Organizations' Agility at https://www.igi-global.com/dictionary/operational-tempo/40065 “You can think of the iterative design process as a continuous cycle of prototyping, testing, and making adjustments and refinements.” from What is Iterative Design? (and Why You Should Use It) at https://www.enginess.io/insights/what-is-iterative-design

In this episode Matt and Mike discuss iterative design. No matter what you're designing, or using, it went through some sort of iterations before coming to market. Something as simple as adjusting a font size contributes an iteration and shows a commitment to make a product better. When it comes to web development, if you're not classically trained in design, or UI/UX then iterative design is your best friend - as long as you do your research and pay attention to other modern UI/UX you'll have a great baseline that you can slowly but surely iterate on to eventually make a production-worthy display.  Then in the Web News, the guys discuss their Top 10 JavaScript open source repos for May 2020 including: reveal.js, ws, Fuse.js, and more! You can find us on... Facebook | Twitter | Instagram RSS | Patreon | Spotify Medium | YouTube | GitHub  Reddit | Discord

Embrace the kind of creativity that's natural to you. You'll make more work, and like it better. Become a supporter on either Patreon or SubscribeStar for over 70 bonus episodes. Follow me on Twitter to check out my art. --- Send in a voice message: https://anchor.fm/whinechamber/message

AC leaves us speechless in their explanation of game poetics: novel game studies research to end all ludology/narratology debates. We chat about how iterative design through Energize and Captain's Gambit bolsters AC's research.   To support AC's kickstarter for Captain's Gambit please visit: http://kck.st/2TAEEeh

In this week’s episode of The Secret Sauce, Senior Designer Ashley Cyborski discusses our iterative design feedback process and how this helps move designs forward to effectively meet our clients’ ideal results. TRANSCRIPT Allison Manley [AM]: Welcome to The Secret Sauce, a short podcast by Palantir.net, that offers a short piece of advice to help your business run a little bit better. I’m Allison Manley, an Account Manager here at Palantir, and today we’re talking with Ashley Cyborski about a good design iteration and feedback process. Ashley Cyborski [AC]: Hi everyone, My name is Ashley Cyborski and I’m a senior web designer here at Palantir. You may remember my other podcast about the benefits of designing in the browser. You should check that one out if you’re a web designer feeling hesitant about taking the leap to HTML and CSS. Today, though, I want to talk about our design feedback process here at Palantir, because it is a bit different than traditional design processes. I’d like to rewind and give you a bit of background. At Palantir we use agile methodologies during our development process. For anyone unfamiliar, agile is a 2 week cycle called a sprint where you prioritize work, complete those tasks, present the work to the client, and receive feedback which you can then incorporate into the next sprint. It is a process of continual improvement and collaboration. Our design feedback process came out of a desire to incorporate that same level of collaboration and continual improvement into the design phases of a project. After a lot of thinking, and quite a bit of inspiration from a webinar by Dan Mall, we came up with a process that is iterative, but accommodates our clients’ needs.  The process isn’t perfect and we are continually working to improve it, but it is a huge improvement from where we were just two years ago. The core principle of our design feedback process is iteration. Though this sounds pretty obvious, it is very different than the traditional design feedback and iteration cycle. In a traditional process you present your work, receive feedback, incorporate that feedback into the design that you had presented, and then re-present your work, around and around until the client decides to approve the design. And though that works quite well for print design, it is counter intuitive to web design, especially when paired with an iterative development process. In our feedback process we often tell our clients to think about moving designs forward. At the start, we present 2 to 4 style tiles to the client. Then, we ask them to choose the “most correct” one to move forward with. The one they chose may not be perfect yet, but through iteration and with the proper input, we move the design closer and closer to that “ideal”. In order to get there, we need that input. We ask our clients to provide feedback on the chosen style tile and the discarded ones. We prompt with questions like “What did you like about this design?”, “What don’t you like about this design?”, and most importantly, “Why?” Our goal is to understand our client’s thoughts and feelings, including what is inspiring them and what is concerning them. We take all that feedback and the selected direction, and begin on the first static comp. We don’t spend our time iterating on the selected style tile.  At this point we repeat the process with static comps. The feedback received during the comp phase is worked into the prototype. From there on out, the prototyping process syncs up with the sprint cycle, and feedback on prototypes is defined and prioritized along with the remaining design tasks and incorporated on a sprint by sprint basis. That was a lot of words to describe how we move the design process forward. You might ask, why don’t we work on one deliverable until it is “perfect” or close to perfect? Well there are a few driving factors. First, our process becomes faster and more efficient because we don’t have to pause the project to work out small, inconsequential details that would otherwise resolve themselves in the future. The entire project doesn’t pause until we get it to some subjectively “perfect” state of design. This is important and unique to web design, because your design will appear on any number of machines, browsers, screen sizes, and with multiple variations of changing content over the course of its life. A website is a living, breathing, changing thing. Second, we can adjust the course of our design as the project moves forward and develops. We aren’t stuck with a decision we made in week 1 of the project, when we learn something new in week 7. Development prioritization can drive design prioritization and the design benefits from active and informed developer feedback and input. This benefits the designer, because we aren’t completing work that ultimately will not be implemented, and benefits our clients because they aren’t paying to design work that ultimately won’t be implemented. Third, we get to the browser faster which benefits both the client and the project. I track some of these in a blog post about designing in the browser, but I’ll recap the main points here. Clients tend to understand designs better once we get into the browser because they are more realistic and interactive which helps clients provide better, and more relevant feedback. In browser designs also foster more productive communication and collaboration with developers and reduce duplicated work. Additionally, designers have more control over the final, implemented design. Finally, and possibly most important to the feedback process, it is easier to implement feedback and iterate on the design system in code than it is across multiple page comps. The feedback changes are instant, consistent, and more efficient. Ultimately, this means that the client is able to provide more realistic and relevant feedback, which can be implemented and iterated on faster and more efficiently, all while the design process flexes and flows with development’s needs and prioritizations. I think I’ve outlined a lot of the benefits of our forward moving design process, but I should caveat that we are still iterating on this process to make it even more efficient and effective. One of the major gaps in this process right now is client education and buy in. It is often hard to convince a client, with little to no experience with web design, to adjust their preconceptions about the design approval process. It is also hard to get buy in, for example, that the homepage static comp does not have to be “perfect” in order to move onto the next deliverable. Clients fear that their feedback will be lost or forgotten or that it isn’t being taken seriously, when they do not see it implemented immediately. Clients often tend to be relatively uncomfortable moving forward with something that is not “Approved” or finalized for these exact reasons. One way we try to counteract that is with documentation, making sure we track and the requests changes and tickets. It is up to the designer to communicate as best we can the benefits of this process to our clients upfront. I really believe that ultimately a client gets a better, more flexible end product when using this process. I’d love to hear other’s experience with a similar process. Whether it is an issue you’ve run into and solved, or just with your own experience with a similar process as a client or designer. Leave a comment on this post or tweet to me @AshleyCyborski. AM: Thanks for listening to this edition of The Secret Sauce. You can find more great tips on our brand spanking new website at palantir.net, and you can also find us on twitter @palantir. Enjoy your day!

Samuel Hulick is a user onboarding expert who runs a popular website called useronboard.com where he deconstructs the initial experience of popular apps and services. I first met Samuel in Amsterdam, where were were both speaking at TNW Europe. We clicked immediately - and bonded over our shared love of great design - and smart design process. If you want to know what goes into creating a great first-time experience, listen in and discover how this tech-savvy designer became a world-class expert in onboarding.

This lecture begins by exploring what a game is (and isn't) and defining the terms "mechanic" and "dynamic". Designers identify the core mechanic and dynamic of a game to help guide iterative playtesting and optimization.

User interface design is an iterative process - the design of Digg and Pownce have been a study in evolution and adaptation. This talk will inspect the why and how of these iterations by looking at specific case studies from the two projects as well as previous client work Daniel has tackled. The case studies will examine specific user interface challenges that have arisen and will chop them up into their various bits. How do I identify a challenge? What is the best approach for getting started? How do I solve the problem conceptually and technically? How will I know if I solved the challenge successfully? Case studies have been selected that are especially pertinent outside of their specific contexts to help you in your everyday UI design. The presentation will focus on design inspiration, decision-making processes, technical solutions, and learning from missteps as part of a designer’s iterative process. Daniel is the creative director at Digg, a founder of Pownce, and a founder of the Canadian web firm silverorange. At silverorange, Daniel worked with a wide range of clients including Mozilla, Ning, Revision3, and Sloan. He’s since been lured to San Francisco after Kevin Rose dangled the prospect of In ‘N Out burgers and the opportunity to develop the user experience for the social news website Digg. As Digg’s creative director, Daniel has helped the site grow from a niche technology news site into one of the leading media services on the web with a massive and passionate community. Recently, along with Leah Culver and Kevin, Daniel helped found Pownce - a social network that lets you share files, events, messages, and links with your friends. Daniel works on feature development and the user interface of Pownce. Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).

User interface design is an iterative process - the design of Digg and Pownce have been a study in evolution and adaptation. This talk will inspect the why and how of these iterations by looking at specific case studies from the two projects as well as previous client work Daniel has tackled. The case studies will examine specific user interface challenges that have arisen and will chop them up into their various bits. How do I identify a challenge? What is the best approach for getting started? How do I solve the problem conceptually and technically? How will I know if I solved the challenge successfully? Case studies have been selected that are especially pertinent outside of their specific contexts to help you in your everyday UI design. The presentation will focus on design inspiration, decision-making processes, technical solutions, and learning from missteps as part of a designer’s iterative process. Daniel is the creative director at Digg, a founder of Pownce, and a founder of the Canadian web firm silverorange. At silverorange, Daniel worked with a wide range of clients including Mozilla, Ning, Revision3, and Sloan. He’s since been lured to San Francisco after Kevin Rose dangled the prospect of In ‘N Out burgers and the opportunity to develop the user experience for the social news website Digg. As Digg’s creative director, Daniel has helped the site grow from a niche technology news site into one of the leading media services on the web with a massive and passionate community. Recently, along with Leah Culver and Kevin, Daniel helped found Pownce - a social network that lets you share files, events, messages, and links with your friends. Daniel works on feature development and the user interface of Pownce. Licensed as Creative Commons Attribution-Share Alike 3.0 (http://creativecommons.org/licenses/by-sa/3.0/).