Make every idea concrete enough to build this afternoon
This is the central concept of the talk and the one most teams get wrong. Ng draws a hard line between vague ideas and concrete ideas. "Let's use AI to optimize healthcare assets" is vague — different engineers would do totally different things, and you can't ship it fast because there's nothing specific to ship. "Let's write software so hospitals let patients book MRI machine slots online to optimize usage" is concrete — engineers can start building it this afternoon. The deceptive trap, in Ng's framing, is that vague ideas get more kudos. Tell your friends you want to use AI to optimize healthcare assets and everyone says it sounds great. He puts it directly: "when you're vague you're almost always right. When you're concrete you may be right or wrong. Either way is fine. We can discover that much faster."