A short thread 🧵on "How identifying a GOAL wrongly created complications for me".

Recently I got all worked up. I had an administration issue which I wanted to solve. So I set up my mind map using @FlyingLogic and went about doing my scenario planning.

It all made me more worked up, cause all the solutions which I was coming up with needed more resources than I have. It needed money and time, which would mean it would derail my efforts for a couple of months.

Also, it was in no way related to my product, it was just an administrative requirement.

After spending a couple of days on the problem, it hit me to rethink my GOAL.

I had indeed identified the GOAL wrongly.

I was troubled to see why couldn't I see the issue as it is? What were the blind spots which didn't let me identify my GOALS correctly?

I saw that the blindspots were my embedded beliefs.

I want to appear cool. It is a mimetic desire which gets embedded into all of us as we see successful people around us constantly messaging on Twitter on " How they did it".

I was subconsciously being a conformist. Instead of solving the problem at hand, I was imagining a solution which I wanted. BIG DIFFERENCE.

This incident has made me think long and hard about analysing my GOALS for all my projects. It is tough to be a non-confirmist. As you are constantly being bombarded with Gurus who keep telling us how they did it and we can do it too.

But without a note of caution that we might end up solving problems which could have a less expensive and efficient way of solving them. The point of writing this thread is to ask the readers what is the process they use to define a GOAL and how do they avoid blindspots?