cross-posted from: https://lemmy.ml/post/54977812
say you want to buy a house, career change, overseas trip, etc.
Sleep on it.
does it help you? what usually happens?
Once nice thing is that your subconscious works on the problem while you’re asleep. For example, I’ve wrestled with an IT problem all night, woke to a solution in my head.
You will be well rested and it lessens the probability of some stupid mistake.
Very few big decisions require an immediate answer, by giving yourself time to think you get past the initial emotional reaction of fomo and into a more logical mindset of how does it fit into my future plan.
I see a lot of useful replies here.
I prefer to answer to 4 simple questions, helps me have a clear idea without overcomplicating:
- What success looks like. Be concrete: “in a year I want X”. If you can’t say it, probably it’s not the right time for the decision.
- The risks. What could go wrong, and how bad would it be? Money, time, people affected.
- The known issues. The problems you can already see today and are choosing to accept.
- The way back. If it goes wrong, how do I undo it, what would it cost, and when will I check? Put a date on it, like “in 3 months I review this”.
The fourth point helps you to determine how “big” the decision is. If it’s easy to reverse, decide fast. If it isn’t, slow down, sleep on it, and talk to someone who has already done it.
If its romance related, jerk off. Makes sure you’re thinking with the right head.
If it can wait a day, take a day, sleep on it. Let your brain ponder as a background process.
At minimum, I spreadsheet my big decisions. I put in all my known factors: budget, TCO, alternatives, a weighted list of pros and cons (weights according to factors important to me or ability to solve the problem at hand), etc.
For really big decisions, I build a decision tree with dynamic branches. For example, when buying my most recent house, i had inputs for interest rate, points, house inspector rating, cost to move my sailboat to my house, average luminous flux received, etc. Data in these fields adjust other fields like TCO and budget, which then shift the decision tree one way or another.
It’s excessive, but I do it this way to help me avoid missing some big variable.
Study the Art of War
I have had people unironically ask me “how can a guy writing about a battlefield apply to my problem? Go away.”
I promise, if you want a solution to a problem, it is applicable.
I tend to think about all options in their wost case scenario (if everything goes wrong), and then check which of the options at their worst I would regret more, and go for the one with least regret.
im future focused so im kinda in a constant state of wondering about possible future decisions I have to make. The more possible and imminent the more I think about it till the decision is made. so not pro tip but more obsession sharing. sorry.
Long term, have a set of ideals for what you want out of life. Your list will be different than others and that is ok.
Short term, identify the costs of the decision. Include opportunity costs for making different decisions. Try to frame the decision, including keeping the status quo, as a cost you are paying for a benefit.
Also, try to have an idea on the overall cost of making the decision is. A lot of people get into analysis paralysis because they try to make the best decision when the time and effort in making the best decision is most costly than making a good decision.
Assign heads yes, tails no. Flip a coin, catch it, cover it. Ask yourself if you’re hoping to see heads or tails. Don’t look at the coin flip result. Do what you were hoping for.
I’m using this :)
Ugh… .ml…
if you want to reply, can we do it here - https://lemmy.ml/post/54977812 - this may help community be active again
Tip #1:
Don’t listen to .ml
Tip #2:
Most people outside of .ml know not to go there, asking people to go there is very unlikely to work. If you want more info on why most people block that whole instance, the basic is your admins are shite
TIL





