[Crossposted from my Substack. The full article can also be found on the EA Forum here.]
Advice is important. It can help you solve a problem, or to make better decisions. But not all advice is equal, and not all advice should be followed. So how can you tell whether (or how much) you should follow a certain piece of advice?
Below you'll find a framework for evaluating advice, and a link to a workbook version you can copy and use. For more detailed information, see the full 'Advice on Advice' article.
The sections below expand on each element of the framework with practical considerations.
Remember: It is still important to appreciate that someone has taken the time to help you, even when evaluating their advice critically. You can value someone's input while still determining how much it applies to your specific situation and how best to implement it.
Key Question:
Do they know my situation, and what assumptions are they making?
Important Considerations:
An Example:
For one-to-many communication (e.g. in an article on the internet), think about the target audience of the piece and what assumptions they are likely to be making about the reader.
Key Question:
Do they have experience in or knowledge of a comparable situation?
Important Considerations:
An Example:
A senior professional may have a lot of very useful expertise about priorities within a field… and less knowledge of the current early-career job hunt.
Key Question:
Why are they giving me the advice, and what are their intentions?
Important Considerations:
An Example:
If someone advises you to ‘just take any job to get started’ in an area, consider whether it might come from their anxiety rather than strategic planning based on your goals.
Key Question:
Would this advice help me achieve my goals, or different goals?
Important Considerations:
An Example:
When considering graduate study to develop practical skills for industry impact, advice you receive about what to prioritise (e.g. teaching experience or maximising publication count) might instead be optimised for academic career advancement.
Key Question:
Which parts of this advice can I apply, and how should I go about applying it?
Important Considerations:
An Example:
When switching careers, advice to join a coding bootcamp contains valuable reasoning about skill development, but you might instead decide to take free online courses and build small projects that help you gain similar skills while better matching your financial situation or learning style.
The context in which you receive advice significantly affects how you should evaluate it, for example:
For more detailed information on the above, particularly on evaluating advice during challenging personal or professional situations, see the full article which explores this in greater depth.
A slightly modified version of the above sections have been summarised into a Google Doc, to make it easier for you to copy and use if you would find it helpful. You can access it here.
The above factors can help you critically evaluate advice that you receive… including this advice itself. Follow this framework to the extent that it is useful for you based on your goals, and use it as a starting point rather than a definitive approach.
If you found this summary valuable, the full ‘Advice on Advice’ article explores several areas in greater depth including: the influence of emotional states on advice, how your background and goals influence advice suitability, approaches to prioritise implementing advice you receive, how crisis situations change both giving and receiving advice, and my reasoning and motivations for putting this together to help you assess its quality.
Executive summary: This post presents a thoughtful, moderately confident framework—the VOWEL framework—for evaluating advice based on factors like source, experience, and relevance to one's goals, along with a practical workbook to help users apply it; the author encourages critical engagement with advice, including their own.
Key points:
This comment was auto-generated by the EA Forum Team. Feel free to point out issues with this summary by replying to the comment, and contact us if you have feedback.