Plan Break Consequences - WIP

[virtual256]

Plan Break Consequences:

I)Intended:

1)Can be part of plan - At this condition, cut & run.
2)With notice, not sudden or defaulted.

a)Notice should be before, if at all possible. If notice is given after, it better be a *damn* good reason.
b)Notice can be as simple as 'Shit, double booked. Change plans to XYZ/reschedule'.
3)Requires an

Comments

[kuangning]

I *like* you, y'know that?

[virtual256]

Yeah. This is just something that was bouncing about in my head, it's actually part of a longer thing, and [III,4.b.ii] isn't complete yet. More written on paper, yet to type and format.

[lintras]

I have an ex-girlfriend who really could've used a look at this.

[zanfur]

I would have organized it slightly differently (for instance, I would have put I and II underneath a common heading of "Motivation for break" or something similar, as "Likely Severity[sic] of break" really doesn't really fit the pattern established by I and II), but the content would be the same.

[virtual256]

*nods* makes sense, this is just how it came out of my head, first version, etc.

Will be edited more.

[dojcjfreak]

Alright I think I understand what this is, very cool. You could use a few more words to make it clear. Like in III) it took me a while to realize that those were the types of plans not the types of breaks. This now makes sense why I generally try to make verbal flimsy plans whenever possible... it means when I'm dumb it causes less pain.

[virtual256]

Oddly enough, the amount of pain from a verbal plan break is way more then you might think. If I get caught in it, I'm stuck there for a while.

Also, the more I plan something, the less likely I am to break that plan. Once a plan gets to the point of being 'Concrete', 'Outs' are planned into it. (At x time, if I'm not here, I won't be. Meet at y time at z place instead.)