Ask Your Developer Flashcards
Quote by Darwin on who survives
It’s not the strongest species that survive, nor the most intelligent, but the ones most responsive to change.
Why does it make sense to give developers problems and not solutions?
First, giving developers solutions violates a principle of human nature. Developers like anyone are motivated by autonomy.
Second, often managers giving developers details specifications or solutions and not problems creates a game of “telephone” where the end product is many steps removed from the customer, and doesn’t meet the customer needs.
How do you re-inforce giving a developer a problem to solve to make sure they fully understand the problem?
Have them directly experience the problem themselves, or directly meet with customers themselves. Removing layers between developers and customers or problems lead to more precise software solutions.
What is the seed analogy as it relates to experiments?
Businesses should plant many seeds, and if they start to grow then water (invest) in the growth, and let the seeds that don’t grow die.
What is extremely important about setting up a small experiment before it starts?
Clearly stating the hypothesis. It is important to understand if the experiment is failing, this can only be done with a clear hypothesis.
What is the “top down innovation model” vs. the “bottom up innovation model”
Top down = idea to change a company comes from the top (or anywhere), but the entire business shifts in a new direction.
Bottom up = small experiments in small teams with clearly defined hypothesis are tested, and those that win and grow are further invested.
What are the downsides of “2 pizza” teams? What is the antidote?
The downside is you may have many teams working without any cross pollination of ideas.
The antidote is to have scheduled formats to communicate what’s going on in the individual teams that don’t take the focus away but educate the entire organization.
