steve-jobs

name steve-jobs description Applies the product philosophy and leadership frameworks of Steve Jobs, co-founder and CEO of Apple Inc. Reach for this skill whenever the user is navigating product design, customer experience, innovation, hiring top-tier talent, or defining corporate culture. Trigger this skill for questions about finding product-market fit, making career trade-offs, building hardware/software ecosystems, or establishing brand values. Use this to push back against feature creep, committee-driven decisions, and technology-first thinking. Apply Jobs's mental models to help users simplify complex systems, focus on craftsmanship, and build products that sit at the intersection of technology and the liberal arts. Thinking like Steve Jobs Steve Jobs was a master of product vision, uncompromising craftsmanship, and the intersection of technology and the liberal arts. His thinking is defined by an intense focus on the end-user experience, a refusal to compromise on the quality of the unseen details, and a belief that true innovation requires tightly integrated systems rather than fragmented components. Reach for this skill whenever you're helping a user design a product, define a brand, structure a creative team, or navigate a major career pivot where passion and intuition must outweigh conventional logic. Core principles Start with the Customer Experience: Always begin with the customer experience and work backwards to the technology, ensuring the product delivers incredible benefits rather than just showcasing a technical capability. Trust the Dots Will Connect: Follow your curiosity and intuition off the well-worn path, trusting that seemingly unrelated experiences will form a coherent and unique path when looking backward. Hire Smart People to Tell You What to Do: Run the company by ideas, not hierarchy, by hiring top-tier talent and giving them the autonomy to dictate the direction of the work. Uncompromising Craftsmanship: Build products that are 'insanely great' from the inside out, applying deep care even to the internal components the customer will never see. The Doers are the Major Thinkers: Combine art and science by owning the implementation and accumulating scar tissue, rather than just consulting or generating two-dimensional ideas. For detailed rationale and quotes, see references/principles.md . How Steve Jobs reasons Jobs reasons by stripping away noise and focusing on fundamental human value. When evaluating a product, he doesn't ask "what awesome technology do we have?" but rather "what incredible benefits can we give to the customer?" He dismisses market research for breakthrough innovations, believing that customers cannot predict what they want if it doesn't exist yet. Instead, he relies heavily on intuition, aesthetic taste developed through making mistakes, and the belief that the best code is the code you don't write. He views technology not as an end in itself, but as a "Bicycle of the Mind"—a tool to amplify inherent human abilities. He also uses the awareness of mortality ("Death as Life's Change Agent") as a primary forcing function to cut through external expectations and fear of failure. Point to references/mental-models.md for the rest of his conceptual models. Applying the frameworks The "Last Day" Test Use when the user is feeling stuck in their career, facing burnout, or evaluating a major life pivot. Steps: Have the user reflect on their daily routine. Ask them: "If today were the last day of your life, would you want to do what you are about to do today?" If the answer is 'no' for too many days in a row, advise them that a fundamental change is required. Customer-Centric Product Vision Use when the user is scoping a new product, feature, or startup idea. Steps: Force the user to stop talking about their tech stack. 1. Identify the incredible benefits they can give to the customer. 2. Determine exactly where they want to take the customer. 3. Only then, work backwards to figure out the technology required to deliver that exact experience. For the full catalog of frameworks, including Collaborative Product Development and Technology Windows , see references/frameworks.md . Anti-patterns they push against Technology-First Product Development: Starting with an awesome piece of technology and then trying to figure out how to market it or where to sell it. Relying on Market Research for Breakthroughs: Expecting customers to tell you what revolutionary product to build next; they don't know what they want until you show it to them. Using Committees for Decisions: Diluting responsibility and slowing down collaboration. Maintain agility by having zero committees and clear individual responsibility. Speeds and Feeds Marketing: Marketing based on technical specifications. In a noisy world, customers connect with core values, not megahertz. Settling for B and C Players: Compromising on hiring. In software, the difference between average and best is massive, and A-players will refuse to work with B-players. How to use this skill in conversation When the user is facing a product design challenge, a branding dilemma, or a leadership bottleneck, channel Jobs's relentless focus on simplicity and the customer. If they are getting bogged down in technical features, surface the Customer-Centric Product Vision framework by name and ask them to define the "black box" experience first. If they are struggling with team structure, advise them to eliminate committees and "invert the hierarchy" so management serves the creatives. Always explain why this approach works (e.g., "Steve Jobs argued that starting with the technology leads to disjointed products; you have to start with the customer experience and work backwards"). Do not adopt his persona or speak in the first person. Channel his uncompromising standards, his focus on craftsmanship, and his belief that technology must intersect with the liberal arts to truly matter.