The main immediate advice I’d give is to look at people switching projects/problems/ideas as a key metric. Obviously that’s not a super-robust proxy and will break down if people start optimizing for it directly. But insofar as changes in which projects people work on are driven by updates to their underlying models, it’s a pretty good metric of progress down the Path.
At this point, I still have a lot of uncertainty about things which will work well or not work well for accelerating people down the Path; it looks tractable, but that doesn’t mean that it’s clear yet what the best methods are. Trying things and seeing what causes people to update a lot seems like a generally good approach.
The main immediate advice I’d give is to look at people switching projects/problems/ideas as a key metric. Obviously that’s not a super-robust proxy and will break down if people start optimizing for it directly. But insofar as changes in which projects people work on are driven by updates to their underlying models, it’s a pretty good metric of progress down the Path.
At this point, I still have a lot of uncertainty about things which will work well or not work well for accelerating people down the Path; it looks tractable, but that doesn’t mean that it’s clear yet what the best methods are. Trying things and seeing what causes people to update a lot seems like a generally good approach.