Code-first vs. Product-first
thezbook.com
Code-first vs. Product-first
Many concepts that sound good on paper are infeasible to implement, or simply don’t produce the expected results. It’s frustrating when that happens, of course, but the pace of experimentation and learning at a startup is unparalleled. I think this is an especially important form of rigor for theorycels like me. Building product forces a different ... See more
Jasmine Sun • exit interview
They are deeply oriented around actual customers and the value their product brings to those customers. They also understand that the product is in service of a business and can incorporate those constraints into the design of the product.
Marty Cagan • INSPIRED: How to Create Tech Products Customers Love (Silicon Valley Product Group)
Changing the product domain made it easier to navigate. You can have two product development processes: Ask customers what problems they have and build for them. Or you don't ask customers anything and rely on internal product leaders' taste and judgment. Customer obsession and taste are parallel paths to product success. Some domains, like Lean St... See more
Cedric Chin • Product Validation Frameworks are Mostly Useless Without Taste
If you want to deliver great products, you want to use best practices for engineering and try not to override the engineers' concerns.
Marty Cagan • INSPIRED: How to Create Tech Products Customers Love (Silicon Valley Product Group)
Today hundreds, sometimes thousands, of people might develop a piece of software. This has led to two things, Saarinen says: a focus on process over product, and removing engineers from positions of influence. “I think people get too focused on the different frameworks and processes,” he says, “and you start to forget, what are you actually doing?
... See more