“The UX team is constantly interviewing and interacting with our users, so they generate a lot of hypotheses which we investigate using our data. The UX team, because their insight is built quickly from human interactions, can flit from thought to thought and project to project; when they think they’re onto something good, they kick the research idea to the lumbering beast that is the data science team. We can comb through our billions of records of sends, clicks, opens, http requests, user and campaign metadata, purchase data, etc. to quantitatively back or dismiss their new thinking.”
– Data Story: John Foreman of MailChimp on the Data Science Behind Emails
The single largest difference I’ve noticed between successful founders and failed ones is hidden between the lines of Graham’s response: it’s knowing how to think. Most people don’t know how to strategize. Most people don’t know how to take what they see in the world and use it to invent something new. Most people don’t take everything they learn, and think “Why?”, “How?”, and “What does this mean for the future?”. But to be a successful executive, you have to ask those questions about everything you read and see, because, if you don’t, you’ll build the wrong thing. Or focus on the wrong thing. Or your competitor will out-innovate you.
There is an insanely huge difference between, “We’re making a site for connecting to your friends” and, “Privacy is a relic of the past, so we’re going to push people to open up their lives and share, connecting them together.”
Most people see Facebook and extrapolate backwards to the first sentence above. But the genius behind Facebook, and why it has been continually successful, is actually in the second sentence. Facebook isn’t about connecting; it’s about sharing. MySpace failed because it focused on the connections, not the interactions between those connections. Facebook had the Wall and the News Feed.”
– Dustin Curtis, Learning how to think
“If you want to make it within what I rather helplessly call the system(s), it’s not recommended to ask fundamental questions. What you should do is ask questions that can be answered. And then you answer them. Especially when you’re socialized in the IT world, you’re prone to solutionism: If there’s a problem, a privately funded company will come up with a (technical) solution to solve it and make people’s lives better. You don’t ask why, you just do.”
– Gabriel Yoran, If you question something, people will question you
“There is an insanely huge difference between, “We’re making a site for connecting to your friends” and, “Privacy is a relic of the past, so we’re going to push people to open up their lives and share, connecting them together.”
– Dustin Curtis, in Learning how to think
'We wanted a service that lets you dine out and pay without waiting for the check,' Cove said. 'Dining out should be about the people at the table around you. We wanted to make it about that experience.'
What they set out to build, then, was a payments platform and mobile application that would reduce all the fuss and calculations that happen when the check comes. It was important to them that the platform would be able to gracefully handle large groups, and also that it would work with restaurants’ existing point-of-sale systems so that they wouldn’t have to install a whole new order, ticket, or payments system.”