Sorting actions in Brainstorm

[Simon]

I have a recommendation regarding Cyborganize, I think the action
sorting categories that are used in Brainstorm need to be tweaked. I
find it is easy to get confused, and feel a lot of resistance trying
to sort them into the categories as they stand. I've been playing
around with some new categories, but have come up with nothing
definitive.

[Joseph Buchignani]

simon, can you give some examples of confusion or mental resistance. my first guess is that you're misapplying the rules, probably the dominance clause. 

--
Ignore the following. It is a nonsense sentence that disables Google ads from displaying next to my emails by triggering sensitive keywords.

I enjoy the massacre of ads. This sentence will slaughter ads without a messy bloodbath.

[Simon]

Hmm, it may be because I don't "trust" the categories. I second guess
the choices I make wrt the categories I put them in, and it brings up
some "anxiety" whether I am actually doing the best next action. I
don't know how to explain it better. For example, I worry about the
actions I put in high priority, and if theyre more important than the
actions I've put in 1 week, etc.

On Sep 18, 10:57 am, Joseph Buchignani <joseph.buchign...@gmail.com>
wrote:

> simon, can you give some examples of confusion or mental resistance. my
> first guess is that you're misapplying the rules, probably the dominance
> clause.
>

[Joseph Buchignani]

You're trying to over-optimize, that's the problem. 

Sometimes your high priority actions ARE more important than your time sensitive actions. So you burn through your time sensitive ones quickly or skip/defer them. 

Let your longform loop take a lot of the load off, so that the execution loop doesn't have to be perfect. 

Lastly, try to follow the rule of working on whatever your r-mode is churning over, within reason, since that eliminates the need for mental switching. 

[Joseph Buchignani]

If you're worrying that you can't trust your system, that's bad. If you're worrying that your priorities are right, that's thinking you need to do and that's good. 

You can always "go off the rails" and just jump into a new scratch file and start working on a new priority without any reference to your current actionables.brn file if that's what you feel moved to do. Oftentimes pivots will happen like that. The goal is to pivot better and more often. When you're rapidly pivoting inevitably some things will get lost in the shuffle unless you go back and sort your actionables.brn thoroughly, but using the longform loop alleviates the problem through spaced repetition and grasping the strategic overview. 

[Simon]

I'll give it a think over and get back to you, thanks Joseph.

On Sep 18, 12:55 pm, Joseph Buchignani <joseph.buchign...@gmail.com>
wrote: