In the fast-paced world of software engineering, developing technical skills often takes precedence. However, if you're seeking career advancement, enhancing your technical skills alone is not enough; you also need to deepen your empathy for users—a skill frequently overlooked in traditional engineering roles. Understanding user needs and the broader impact of your work will not only lead to better products but will also help your career grow and flourish.

Drawing on over 20 years of experience, including roles at Microsoft, Facebook, Stripe, and Temporal Technologies, author Drew Hoskins guides you through the essential strategies to bridge the gap between engineering prowess and product insight. Whether you're building consumer products, tools for professionals, or internal platforms, this book is your gateway to becoming a well-rounded engineer who sees around corners and innovates according to user needs.

• Simulate and predict user interactions to enhance product usability
• Sharpen your focus on the specific needs of your target audience
• Engage with users effectively to gather impactful feedback
• Prioritize your time and product roadmap strategically based on cost and impact

Osoby które kupowały "The Product-Minded Engineer. Building Impactful Software for Your Users", wybierały także:

• Jak zhakowa 125,00 zł, (10,00 zł -92%)
• Biologika Sukcesji Pokoleniowej. Sezon 3. Konflikty na terytorium 117,27 zł, (12,90 zł -89%)
• Windows Media Center. Domowe centrum rozrywki 66,67 zł, (8,00 zł -88%)
• Podręcznik startupu. Budowa wielkiej firmy krok po kroku 92,14 zł, (12,90 zł -86%)
• Ruby on Rails. Ćwiczenia 18,75 zł, (3,00 zł -84%)

Spis treści

The Product-Minded Engineer. Building Impactful Software for Your Users eBook -- spis treści

• Preface
  • Why This Book Exists
  • Who This Book Is For
  • Structure of the Book
    • The Double Diamond Process Model
    • The Parts
    • The Chapters
  • Content Notes
  • Conventions Used in This Book
  • OReilly Online Learning
  • How to Contact Us
  • Acknowledgments
• 1. The Foundations of Product Thinking
  • Case Study
  • The First Attempt, with No Scenarios
    • Meh Results
    • What Went Wrong?
  • A Second Attempt with Scenarios
  • Scenarios as Stories That Inspire
  • Scenarios That Capture User Interviews
  • Scenarios That Highlight Product Gaps
  • Scenarios That Highlight a Frictionful Experience
  • Scenarios That Validate the Feature Youre Planning to Build
  • Scenarios as Tests
  • Searching for the Key Answers
  • So, Whats the Scenario?
    • A Motivation
      • Authoring a motivation
    • A Persona
      • Authoring personas
      • Determining a personas means
      • Character summary
    • A Simulation
      • Authoring a simulation
    • How to Use Scenarios?
  • Chapter Summary
  • Exercises
  • Answers
• I. Develop
• 2. Guiding Users Through Your Product
  • Case Study Introduction
  • Scenarios in the User Journey
  • The Discovery Scenario
    • Product Discovery Mapping
    • Leverage Users Knowledge
    • Offer Multiple Routes to Discovery
    • Gracefully Reveal Complexity
    • Multipersona Design
    • Turn Unknown Unknowns into Known Unknowns
  • The Understanding Scenario
    • Picking Understandable Names
    • Classic Naming Advice Revisited
      • Avoid ambiguity (instead of be self-explanatory)
      • Trade off consistency with specificity (instead of be consistent)
      • Only use acronyms and abbreviations that are ubiquitous for your target persona (instead of avoid acronyms and abbreviations)
      • Convey only what users need to know (instead of be concise)
    • Giving Redundant Explanations
  • The Usage Scenario
  • Optimizing the Whole User Journey
  • The Limits of Signifiers
  • Chapter Summary
  • Exercises
  • Answers
• 3. Errors and Warnings
  • The Value of Diagnostics
  • Scenarios for Diagnostics
  • Categorizing Error Scenarios
    • Categorizing Errors in Practice
  • Warning and Error Messages
    • Case Study Introduction
    • Provide Context
      • Echo the relevant data
      • Provide a detailed reason
      • Remind the user what they did
    • Make Error and Warning Messages Actionable
  • Raise Errors at the Interface
    • Upfront Validations
    • Repackage Errors
  • Raise Programmable Errors
    • Raise Specific Errors
    • Group Errors According to Scenario Category
    • Keep Information Around for Diagnostics
      • Pass around high-level abstractions
      • Add structured metadata
      • Persist extra context
  • Diagnose Early
    • Do Static Validations
    • Validate Upfront
    • Let Them Test
    • Request User Confirmations
  • Chapter Summary
  • Exercises
  • Answers
• II. Deliver
• 4. Experiencing Your Own Product
  • Tests as Dogfooding
    • What Kinds of Tests Should You Write?
      • Choosing test types
      • Test only what users care about
    • Scenario Tests
    • Functional Tests
    • End-to-End Tests
    • User Acceptance Testing
  • Documentation-Driven Development
    • Documentation Shouldnt Be Load Bearing
    • Scenarios for Documentation Readers
      • Discovery
      • Learning
      • Usage
      • The web of documentation
    • Writing Documentation as Dogfooding
  • Friction Logging
    • Writing Friction Logs
    • Receiving Friction Logs
    • Friction Logging Culture
  • Samples
  • Chapter Summary
  • Exercises
  • Answers
• 5. Keeping Up with Users
  • A New Job DescriptionDigital Twin Caretaker
  • Designing for Change
    • Case Study Introduction
      • Developer productivity engineering
      • Analysis paralysis
    • The Technological Underpinnings of Change
      • Find the time to improve
      • Technology shapes culture
  • Getting User Feedback
    • Beta Versions Lower the Blast Radius of Failures
    • Feedback Widgets Help People Raise Their Voices
    • Champions Programs Offer Depth
    • Surveys Offer Breadth
    • The User Support Flywheel
      • Eliminate barriers to entry
      • Be gracious
      • Explore the users scenario
      • Start by unblocking the user
      • Ask: how could your product have served the user better?
      • Scaling support while keeping your direct connection to users
      • Providing support when there are added layers
      • The power of user support
  • Product Metrics
    • Case Study Introduction
    • Adoption Metrics
    • Value Metrics
    • Key Performance Indicators
    • Tactical and Strategic Metrics
  • Chapter Summary
  • Exercises
  • Answers
• III. Discover
• 6. Understanding Your Target Audience
  • Real Users, Not Straw Men
  • Case Study Introduction
  • Stand Back, Wield Science
  • Customer Discovery
    • Getting Interviews
    • Customer Discovery Interviews
      • The customer interview funnel
      • Scripting your questions
      • Response analysis
    • Sales Calls
    • Customer Discovery Surveys
    • Networking with Interviewees
    • Customer Interviews Rules of Thumb
  • Crafting and Communicating a Target Audience
    • Choosing a Target Audience
    • Gaining Alignment with Personas
    • Audiences for the App Center
    • Nonpersonas
  • Selecting Features Based on a Target Audience
    • Keeping Your Focus
  • Multipersona Products
    • When Personas Are in Conflict
    • Understanding the Value of a Customer
    • Prioritizing Among Competing Personas
  • Chapter Summary
  • Exercises
  • Answers
• 7. Discovering Your Product Through Simulation
  • From Vision to Requirements
  • Case Study Introduction
    • AI Assistant Product Brief
      • Product thesis
      • Antitheses/risks
      • Target audience
      • Product goals
      • North star scenarios
  • Finish Your Product Vision with North Star Scenarios
    • Scenario-Driven Discovery
    • Brainstorm Scenarios as a Team
    • Select and Refine the North Star Scenarios
  • Convert the North Star Scenarios into Requirements
    • High-Level Requirements
    • The Product Requirements Document
    • Use Case Compendium
    • Organize Your Use Case Compendium
  • Prioritize the Requirements for Your First Milestone
    • What Really Matters for Prioritization?
      • Optimizing for buck
      • Optimizing for bang
        • Scale is hard
        • User value is back-loaded
        • Competitive differentiation is even more back-loaded
        • Sustaining value over time is hard
      • Combining bang and buck
    • Define the Target North Star Scenarios for Your First Milestone
    • Prioritize the Use Case Compendium
  • Build Detailed User Flows for Your First Milestone
    • Validating User Flows
      • Requests for comment
      • Usability studies
  • Translate User Flows into Jobs to Be Done
  • Feeding Back into the Requirements
  • Chapter Summary
  • Exercises
  • Answers
• IV. Define
• 8. Interaction Design
  • The Role of Bias and Ideology in Software Design
    • Debate: Flexible Versus Opinionated
    • Debate: Optimism Versus Pessimism
    • Debate: Open Source Versus Proprietary
  • The Prerequisites of Good Design
  • Case Study Introduction
  • Call Attention to the Correct Usage of Your Product and Away from Incorrect Usage
    • Choose Safe, Predictable Defaults, or None at All
    • Optimize Your Path of Least Resistance
    • Give Affordances to the Right Persona in the Right Scenario
    • Perform Validations
  • Time the Affordances You Ship Wisely
    • If Its Worth Building, Its Worth Validating
    • Be Neither an Optimist nor a Pessimist
    • Apply the Rule of Three
    • Build It in Stages
    • If Necessary, Start with an Experimental Version
  • Narrow Versus Extensible Features
  • Chapter Summary
  • Exercises
  • Answers
• 9. Product Architecture
  • The Foundations of Product Architecture
    • Zoom Out and Look at the Big Picture
    • Avoid the Streetlight Effect
    • Communicate the User Impact of a Proposal
    • Use Technologies That Bridge the System-Product Gap
  • Case Study Introduction
  • Reliable User Experiences
    • Latency
    • Availability
    • Data Consistency
    • Latency, Availability, and Data Consistency Trade-Offs
  • Scalability
    • Scale Simulations
      • Scale simulation tips
      • Bridging technologies
  • Communicating Nonfunctional Requirements to Users
  • Chapter Summary
  • Exercises
  • Answers
  • Wrap-Up
• Index