May 6, 2021 — I split advice into two categories:
WeakAdvice:
🥠 Reading is to the mind what exercise is to the body.
🥠 Talking to users is the most important thing a startup can do.
StrongAdvice:
💎📊🧪 In my whole life, I have known no wise people (over a broad subject matter area) who didn't read all the time – none, zero. Charlie Munger
💎📊🧪 I don't know of a single case of a startup that felt they spent too much time talking to users. Jessica Livingston
If you only look at certain dimensions, you may conclude the WeakAdvice is better.
WeakAdvice is shorter and does not have an author's name.
But all things considered, StrongAdvice is 100x better.
StrongAdvice is advice that is concise, derived from data, and easy to falsify.
Unlike WeakAdvice, StrongAdvice needs to be backed by a large dataset.
In 2009 I wrote:
🥠 to master programming, it might take you 10,000 hours of being actively coding or thinking about coding.
Ten years later, I now have the data to write:
💎📊🧪 Every programmer I respect the most has practiced more than 30,000 hours[1].
Even though the message is the same, the latter introduces a dataset to the problem and is instantly testable.
StrongAdvice can't just be the inclusion of a dataset. It should be constructed to provide instant testability.
Without the testability Munger's quote would be WeakAdvice:
🥠 I've met hundreds of wise people who read all the time
A testable version is a 1,000x stronger signal. If Munger, who likely met more wise people than nearly anyone, never came across an instance of someone wise who didn't read all the time, it's a pretty strong signal that reading is a requirement for being wise.
Versus the WeakAdvice version, which would also be true if it was just a slight correlation.
Sometimes you see WeakAdvice evolve into StrongAdvice, where an advisor hasn't quite made it instantly testable yet but is proposing a way for the reader to test:
💎📊 If you look at a broad cross-section of startups -- say, 30 or 40 or more; which of team, product, or market is most important?...market is the most important factor in a startup's success or failure. Marc Andreessen
Coming up with StrongAdvice requires time.
Like a good Proof of Work algorithm, StrongAdvice is hard to generate but easy to test.
I know Charlie Munger has met thousands of "wise people". All it would take would be for me to find just a single one that didn't read all the time to invalidate his advice. But I can't.
I know Jessica Livingston knows thousands of startups and I just need to find one who regrets spending so much time talking to users. But I can't.
If you have a lot of experience, I urge you to chew on your WeakAdvice until you can form it into StrongAdvice.
StrongAdvice is perhaps the most valuable contribution to our common blockchain.
My back of the envelope guess is that 99.9% of advice is written in WeakAdvice.
WeakAdvice is valuable for changing your perspective.
WeakAdvice is good for ideating.
Nothing wrong with WeakAdvice.
But it's worth a lot less than StrongAdvice.
Mistakes happen when people treat WeakAdvice like StrongAdvice.
Bad advice is a mistake on the reader's part, not the writer's.
Most "bad advice" has a famous person on one end, simply because they are constantly hounded for advice.
Mostly they'll give out WeakAdvice, since new StrongAdvice take time to create.
When you can quickly identify the difference between WeakAdvice and StrongAdvice, you're less likely to make the mistake of blindly betting on WeakAdvice.
It's safe to use WeakAdvice for ideating but not for decision making.
StrongAdvice you can bet on.
[1] There are a lot of programmers who have 10,000 hours of experience that I respect a lot and enjoy working with, but the ones I study the most are the ones who stuck with it (and also just lucky enough to live long lives).