Quotes

  1. A key premise for the next decade: it’s easier for software to enter other industries than for other industries to hire software people.

  2. Projects usually start by listing out the team’s assumptions. However, they aren’t always labeled as ‘assumptions.’ Instead, they are often labeled as ‘requirements.’

    Even worse, these ‘requirements’ aren’t ever questioned or tested. Validation is considered harmful to the project.

  3. Innovative designs don’t happen because of a single smart person who drives everything the team does. Innovation happens when the team creates an environment where small, powerful ideas can float to the top.

  4. In terms of boring conversations that have the potential to be interesting, Mass Indie is like talking about the dream you had last night, whereas Normcore is like talking about the weather.

  5. You’re so special nobody knows what you’re talking about.

    It’s the potluck where the guests have so many dietary restrictions, that everyone can only eat what they brought. It’s the party that’s so exclusive that no one even shows up. This is some Tower of Babel shit.

  6. The consistency of normalcy improves the experience of living with the objects, because the longer we spend in contact with the products of design, the more their willful attempts at individualism irritate us.

  7. There are better ways to design than putting a lot of effort into making something look special. Special is generally less useful than normal, and less rewarding in the long term. Special things demand attention for the wrong reasons, interrupting potentially good atmosphere with their awkward presence.

  8. As a founder you have to be kinda delusional because you can be talked out of anything. At a certain point, you have to believe.

  9. Things that really matter are

    • making things that you are actually proud of and
    • making decisions that you are proud of
    • and working with good people

    These are the things that are priorities!

  10. Innovative designs don’t happen because of a single smart person who drives everything the team does. Innovation happens when the team creates an environment where small, powerful ideas can float to the top.

  11. To start a successful freelance writing career, you either need to be independently wealthy or have a very understanding spouse.

  12. When you’re designing something, imagine you’re sitting in a room, helping a real person with the task at hand.

  13. “People come to us and say, ‘We’ve got this problem,’ and we’re immediately assuming that they’re asking us to come up with a solution. Whereas, the right answer is to say, ‘That’s an amazing problem. I don’t know the answer. Let’s figure that out together. Let’s work on that together. Let’s figure out what the best solution might be.”

    “We just don’t have the confidence to do that, because we were told right from the get go when we start school, that there’s only one answer for something. You get given a math test, and the math test says there’s a right answer and a wrong answer. You get given an English test and there’s a right answer and a wrong answer.”

    “We grow up with this belief that there are only answers. Instead of saying, ‘I don’t know, but here’s something else that we could consider.’ Or, ‘Let’s talk about that and come up with the best answer.’ We’re predisposed to think that for every problem out there, there has to be an answer and we’re supposed to carry that in our back pocket.”

    “Whereas in truth, we don’t know what the answers are, especially in this ambiguous future. How could I have possibly known that there were going to be this many devices available in 2016? How was I supposed to know that entire industries’ markets were going to be disrupted by simple ideas?”

  14. It is all well and good to talk about how you are using agile methods or implementing devops, but if your development budget doesn’t have a line item for iteratively improving the apps you just launched, you really are stuck in the past.

  15. Design Walkthrough—How does the design match up with the business problems we’re working to solve?

    Design Review—Is this design ready for moving forward or are their still issues to resolve?

    Design Demo—What is the user’s experience when using this design?

    Design Critique—What can we learn from this design we’ve created?

  16. When you’re a designer who’s been working on a project for a year or two, it’s very easy to think things are intuitive or obvious that are actually totally incomprehensible.

  17. Resist the urge to use text if there are ways to show rather than tell. Use text to prompt the “cause,” and let the user observe the “effect” by doing. [re: app onboarding]

  18. Most artifacts are thrown away, having the ideas in them deemed ‘not worthy of further contemplation.’ But, the process of creating them, critiquing them, and discussing their implications lives on. They become the basis to the teams common understanding of the problem.

  19. “Listen bub,” I say, “it is very impressive that you can teach a bear to ride a bicycle, and it is fascinating and novel. But perhaps it’s cruel? Because that’s not what bears are supposed to do. And look, pal, that bear will never actually be good at riding a bicycle.”

    This is how I feel about so many of the fancy websites I see. “It is fascinating that you can do that, but it’s really not what a website is supposed to do.”