This is great! I love the simplicity and how fast and frictionless the experience is.
I think I might be part of the ideal target market, as someone who has long wanted to get more into the habit of concretely writing out his predictions but often lacks the motivation to do so consistently.
Thank you! I’m interested to hear how you find it!
often lacks the motivation to do so consistently
Very relatable! The 10 Conditions for Change framework might be helping for thinking of ways to do it more consistently (if on reflection you really want to!) Fatebook aims to help with 1, 2, 4, 7, and 8, I think.
One way to do more prediction I’m interested in is integrating prediction into workflows. Here are some made-up examples:
At the start of a work project, you always forecast how long it’ll take (I think this is almost always an important question, and getting good at predicting this is powerful)
When you notice you’re concerned about some uncertainty (e.g. some risk) you operationalise it and write it down as a question
In your weekly review with your manager, you make forecasts about how likely you are to meet each of your goals. Then you discuss strategies to raise the P(success) on the important goals
When there’s a disagreement two team members about what to prioritise, you make operationalise it as a forecasting question, and get the whole team’s view. If the team as a whole disagrees, you look for ways to get more information, or if the team agrees (after sharing info) you follow that prioitisation
If anyone that either has prediction as part of workflows or would like to do so would be interested in chatting, lmk!
This is great! I love the simplicity and how fast and frictionless the experience is.
I think I might be part of the ideal target market, as someone who has long wanted to get more into the habit of concretely writing out his predictions but often lacks the motivation to do so consistently.
Thank you! I’m interested to hear how you find it!
Very relatable! The 10 Conditions for Change framework might be helping for thinking of ways to do it more consistently (if on reflection you really want to!) Fatebook aims to help with 1, 2, 4, 7, and 8, I think.
One way to do more prediction I’m interested in is integrating prediction into workflows. Here are some made-up examples:
At the start of a work project, you always forecast how long it’ll take (I think this is almost always an important question, and getting good at predicting this is powerful)
When you notice you’re concerned about some uncertainty (e.g. some risk) you operationalise it and write it down as a question
In your weekly review with your manager, you make forecasts about how likely you are to meet each of your goals. Then you discuss strategies to raise the P(success) on the important goals
When there’s a disagreement two team members about what to prioritise, you make operationalise it as a forecasting question, and get the whole team’s view. If the team as a whole disagrees, you look for ways to get more information, or if the team agrees (after sharing info) you follow that prioitisation
If anyone that either has prediction as part of workflows or would like to do so would be interested in chatting, lmk!