# product-wisdom > Apply legendary founder wisdom to product creation, design, and building. Use when designing products, making product decisions, prioritizing features, or thinking like Jobs, Bezos, Musk, and other product masters. - Author: prithivraju - Repository: prithivraju/be-curious- - Version: 20260206220116 - Stars: 0 - Forks: 0 - Last Updated: 2026-02-06 - Source: https://github.com/prithivraju/be-curious- - Web: https://mule.run/skillshub/@@prithivraju/be-curious-~product-wisdom:20260206220116 --- --- name: product-wisdom description: Apply legendary founder wisdom to product creation, design, and building. Use when designing products, making product decisions, prioritizing features, or thinking like Jobs, Bezos, Musk, and other product masters. --- # Product Wisdom Skill Legendary founder wisdom for building **insanely great** products. > "A great product has to be better than it has to be." — David Senra --- ## The Product Masters ### Steve Jobs — Apple **Philosophy:** Insanely Great | Principle | Application | |-----------|-------------| | **"Insanely great"** | Good isn't good enough; products must WOW | | **Simplicity is sophistication** | If it needs a manual, the design failed | | **Start with experience** | Work backward from user delight to technology | | **Say NO** | Focus means killing 1000 great ideas | | **Control everything** | Own the full stack for seamless experience | | **Details matter** | Even unseen parts should be beautiful | | **Show the future** | Don't ask customers—show them what they need | **Jobs Maxims:** - *"Quality over quantity. One home run beats two doubles."* - *"If your product improves lives, you have a moral obligation to market it."* - *"Real artists ship."* --- ### Jony Ive — Apple Design **Philosophy:** Less is More | Principle | Application | |-----------|-------------| | **Remove complexity** | Strip to reveal core function | | **Intuitive use** | Products should be obvious to operate | | **Emotional connection** | Design should evoke feelings | | **Craftsmanship** | Understand materials by working with them | | **Timeless aesthetics** | Transcend trends with clean lines | | **Making = Designing** | You can't design what you don't build | **Ive Maxims:** - *"True simplicity comes from conquering complexity, not ignoring it."* - *"Care about things most people don't see."* --- ### Jeff Bezos — Amazon **Philosophy:** Customer Obsession + Day 1 | Principle | Application | |-----------|-------------| | **Obsess over customers** | Not competitors—customers | | **Work backward** | Start from customer needs, then build | | **Day 1 mentality** | Always think like a startup | | **Invent on their behalf** | Anticipate needs they can't articulate | | **Long-term thinking** | Make investments that pay off in years | | **Resist proxies** | Process should serve customers, not replace judgment | | **Embrace experimentation** | Fail fast, learn faster | **Bezos Maxims:** - *"Customers are beautifully, wonderfully dissatisfied—always."* - *"Day 2 is stasis, then irrelevance, then painful decline, then death."* - *"If you're competitor-focused, you wait. If you're customer-focused, you pioneer."* --- ### Elon Musk — Tesla, SpaceX **Philosophy:** First Principles + The Algorithm | Principle | Application | |-----------|-------------| | **First principles** | Break to fundamental truths, rebuild from there | | **Question everything** | Challenge every requirement and assumption | | **Delete parts** | Best part is no part. Best process is no process. | | **Simplify then optimize** | Only after removing the unnecessary | | **Accelerate cycle time** | Speed is a feature | | **Automate last** | Never automate a bad process | **Musk's 5-Step Algorithm:** 1. **Make requirements less dumb** — Question everything 2. **Delete the part/process** — If not adding back 10%, you didn't delete enough 3. **Simplify and optimize** — After deletion, not before 4. **Accelerate cycle time** — Go faster 5. **Automate** — Only after steps 1-4 **Musk Maxims:** - *"The best part is no part. It weighs nothing, costs nothing, can't go wrong."* - *"If you're not adding things back at least 10% of the time, you're not deleting enough."* --- ### Enzo Ferrari **Philosophy:** Racing is Everything - Singular obsession with one thing - Sacrifice everything for the mission - Build the BEST, not the most - *"I don't make cars to make money. I make money to make cars."* --- ### Walt Disney **Philosophy:** Quality Will Out - Obsess over guest experience - Never stop improving - Plus it (make it better than expected) - *"We don't make movies to make money. We make money to make movies."* --- ### Henry Ford **Philosophy:** Service Creates Demand - Make products affordable to everyone - Money follows service - Never stop hustling - *"Monopoly is bad. The lack of necessity to hustle is bad."* --- ## Product Creation Framework ### Phase 1: Vision | Question | Framework | |----------|-----------| | What problem are we solving? | First Principles | | Who are we building for? | Customer Obsession | | What would "insanely great" look like? | Jobs Standard | | What does the user FEEL when using it? | Emotional Design | ### Phase 2: Design | Question | Framework | |----------|-----------| | What can we remove? | Musk Algorithm, Ive Simplicity | | Is the experience intuitive? | Jobs "No Manual" Test | | Do the details show care? | Ive Craftsmanship | | Are we controlling the full experience? | Jobs Integration | ### Phase 3: Build | Question | Framework | |----------|-----------| | Are we questioning every requirement? | Musk Step 1 | | What would break if we deleted this? | Musk Step 2 | | Can we accelerate? | Musk Step 4 | | Is this Day 1 quality? | Bezos Standard | ### Phase 4: Ship | Question | Framework | |----------|-----------| | Would Jobs ship this? | "Real artists ship" | | Is it better than it has to be? | Senra Standard | | Are we serving the customer? | Ford, Bezos | | What comes next? | Disney "Plus It" | --- ## Quick Decision Filters ### Should I add this feature? 1. Does the customer need it? (Bezos) 2. Does it simplify or complicate? (Jobs/Ive) 3. Can it be deleted instead? (Musk) 4. Is it insanely great or just good? (Jobs) ### Is this design ready? 1. Would Jony Ive approve the details? 2. Does it need a manual? (If yes, redesign) 3. Does it evoke the right feeling? 4. Is the complexity conquered or ignored? ### Should I ship now? 1. Real artists ship (Jobs) 2. Is it better than it has to be? (Senra) 3. Will customers be delighted? (Bezos) 4. Day 1 bias for action --- ## The Ultimate Product Test Ask yourself these 5 questions: 1. **Would Steve Jobs call this "insanely great"?** 2. **Would customers pay for this even if a competitor gave theirs away free?** 3. **Would Jony Ive approve every detail?** 4. **Did we delete enough? (Added back 10%?)** 5. **Is this a Day 1 product or a Day 2 product?** If any answer is NO, keep iterating. --- ## Example Usage **Input:** "I'm designing a new feature for my app. How should I think about it?" **Response using Product Wisdom:** Let's apply legendary founder thinking to your feature: **1. Steve Jobs Test:** - Is this "insanely great" or just "good enough"? - Can users figure it out without instructions? - Are you saying NO to everything else to focus on this? **2. Elon Musk Algorithm:** - Question the requirements. Who asked for this? Why? - What can you DELETE? Best feature is often no feature. - Simplify before optimizing. **3. Jeff Bezos Filter:** - Are you working backward from customer needs? - Or forward from what's easy to build? - Would this delight a "wonderfully dissatisfied" customer? **4. Jony Ive Lens:** - Have you conquered the complexity or just hidden it? - Do the details show care? - What does the user FEEL when using this? **5. Ship Test:** - Real artists ship. Is this ready? - Is it better than it has to be? --- *Wisdom from: Founders Podcast (David Senra), The Knowledge Project (Shane Parrish), and the biographies of history's greatest product builders.*