Ryan Singer

@rjs

Product strategy at Basecamp

Chicago, IL
Joined November 2007
278 Photos and videos Photos and videos

Tweets

You blocked @rjs

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @rjs

  1. Retweeted
    Jun 4

    Sign of a conceptual breakthrough: When you share it, people think: "Aha! . . . but of course. Why didn't I see that before?"

    1 reply 12 retweets 29 likes
  2. May 30

    "... in a quiet room, with a few trusted colleagues, thinking and talking, and allowing the obvious to show itself."

    1 reply 1 retweet 12 likes
  3. May 26

    "In science you need to understand the world; in business you need others to misunderstand it." -

    6 retweets 33 likes
  4. May 25

    Nice how Stripe gives examples of why different companies use these features of Connect (from )

    3 retweets 35 likes
  5. May 24

    Early prototype of some new marketing for Basecamp based on the customer interviews we did in April. Focused on situations, not features.

    2 replies 4 retweets 50 likes
  6. May 23

    "Ways to use a screwdriver." From an internal post today framing some jobs-to-be-done work we've done recently:

    3 replies 32 retweets 120 likes
  7. May 21

    "Work is the constrained release of energy into a few degrees of freedom." - Stuart Kauffman

    5 retweets 30 likes
  8. May 19

    More specifically, Taylor series is a metaphor for scope. A scoped design can perfectly fit core cases and bad fit beyond them is expected.

    1 reply 8 retweets 48 likes
  9. May 18

    The Taylor series is a nice metaphor for design. Fitting supply to demand gradually, step by step, only succeeding within a specific scope.

    2 replies 4 retweets 21 likes
  10. May 18

    Another beautiful visual explanation from , this time on Taylor series:

    2 retweets 11 likes
  11. May 18

    Some nice charming UI details on the redesign of Things by Cultured Code:

    1 reply 1 retweet 21 likes
  12. Retweeted
    May 17

    Uncover JTBD - then Use contrast to drive prototyping (rather than preference) to create understanding to make critical trade-off decisions

    1 reply 3 retweets 19 likes
  13. May 17

    Demand isn't what people say they want. It's what they do. What they actually do reveals the trade-offs and value behind design problems.

    3 replies 61 retweets 159 likes
  14. May 17

    The minivan proves user opinions have little to do w/ design trade-offs. $5bn market for a product nobody wants going in. (via )

    10 retweets 23 likes
  15. May 17

    The definition of value that informs trade-offs comes from the *situation* users are going through. Not their opinions or ours.

    9 retweets 28 likes
  16. May 17

    Design is about either/or choices. What informs choices? Value. How do teams define what's valuable? "Expert" opinion? Consensus? Seniority?

    2 replies 4 retweets 20 likes
  17. May 17

    In theory designers/product owners understand the demand. In reality they usually don't. Difficulty making trade-offs is evidence of this.

    1 reply 8 retweets 26 likes
  18. May 17

    Facing trade-offs means facing our own understanding. We can't choose when we don't honestly know what is valuable or what matters most.

    2 retweets 19 likes
  19. May 17

    Too many design problems come from assuming every case has to be equally handled. Being better/worse at specific things is part of the game.

    19 retweets 62 likes
  20. May 17

    When stuck in a design problem: (1) make the trade-offs explicit and (2) explicitly define what's valuable to weigh them against each other.

    1 reply 2 retweets 32 likes

@rjs hasn't Tweeted yet.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·