I played around with understanding intuitions today and learnt a few things.
I noticed that I had an active conflict I could experiment with and while I was thinking of trying something simpler, I thought I’d have a go and see what I learn.
The problem was replying to an offer for some work (I freelance). I want to get back to the person asap, but it’s been about 2 days, which is getting to be too long. It wasn’t obvious straight away but I realised I was conflicted about taking the work because I had a slightly flexible prior commitment on the same day. Usually it’s easy to reply with yes or no.
I started off by just brainstorming my thoughts. This ended up being a mix of pros and cons for and against taking the work. (I’m not going to share details for privacy reasons.) I realised that that wasn’t necessarily going to be that useful, because I wasn’t just trying to see the pros and cons. Like it was kind of useful, but it wasn’t really what I was trying to do.
Then I brainstormed my options. But then I realised that this isn’t what I wanted to know either. What I wanted to know was what the situation was that was causing the conflict, and then I wanted to brainstorm variations of that situation. I’m mainly interested in learning about that process. This seems obvious in hindsight, and silly that I didn’t see it sooner, but I saw it after a few false starts.
So I learnt that being able to articulate the scenario causing the conflict is one skill. That’s the first step I would try next time, not brainstorming options or my thoughts (though I don’t think those would hurt to do). If anything, I’d brainstorm ways to describe the scenario. I had success doing this quickly. I can imagine for some conflicts, it could be harder or easily to describe the scenario.
The next step was to think about ways to vary the situation that seem relevant to the conflict. I had success with this and found 4 key aspects to vary, and 2 of those also had nested variable details. So being able to think of ways to vary a scenario is also another skill.
One of the aspects was the specifics of the work. The place, complexity, and pay. I started of with giving myself 3 options {low, medium, high} for the complexity and pay. I realised this made the amount of scenarios pretty big, and with too much detail. Like if one option was a no for the high complexity, high pay, then it’d also be a no for the high complexity, medium and low pay. Like there were some redundant options. I thought, in this case, reducing the amount of options to just {high, low} was fine and if I wanted more detail I could add it later. So starting off more coarse grained was what I learned.
I’ve realised that I need some more details about the prior commitment I had on the day, so that I can make a decision. Importantly as regards philosophy I think I learned some things about the process in a cool way (like I got to see why to do it a certain way by making some mistakes along the way, not just taking someone’s word for a process.) There is more stuff for me to figure out. But I found some sub-skills that I can think about and work on. That’s breaking the skill down further.
Writing a summary like this of work that I’ve done without sharing details is also something I haven’t done that I’m trying out. I think it’s worked okay for a first try. Usually I combine the working with the sharing, if that makes sense.