 
  
      “Product requirements conversations must then be grounded in business outcomes: what are we trying to achieve by building this product? This rule holds true for design decisions as well. Success criteria must be redefined and roadmaps must be done away with. In their place, teams build backlogs of hypotheses they’d like to test and prioritize them based on risk, feasibility, and potential success.”
    
― Lean UX: Applying Lean Principles to Improve User Experience
  ― Lean UX: Applying Lean Principles to Improve User Experience
      “It’s often the case that teams working in agile processes do not actually go back to improve the user interface of the software. But, as the saying goes, “it’s not iterative if you only do it once.” Teams need to make a commitment to continuous improvement, and that means not simply refactoring code and addressing technical debt but also reworking and improving user interfaces. Teams must embrace the concept of UX debt and make a commitment to continuous improvement of the user experience.”
    
― Lean UX: Applying Lean Principles to Improve User Experience
  ― Lean UX: Applying Lean Principles to Improve User Experience
      “Generally, hypothesis statements use the format: We believe [this statement is true]. We will know we’re [right/wrong] when we see the following feedback from the market: [qualitative feedback] and/or [quantitative feedback] and/or [key performance indicator change].”
    
― Lean UX: Applying Lean Principles to Improve User Experience
  ― Lean UX: Applying Lean Principles to Improve User Experience
Julian’s 2024 Year in Books
Take a look at Julian’s Year in Books, including some fun facts about their reading.
More friends…
Favorite Genres
Polls voted on by Julian
Lists liked by Julian

 Sign in with Facebook
Sign in with Facebook
 
    










