I wrote a post last year on two different kinds of expectations: anticipations and entitlements. I realized sometime later that there is a third, very important kind of expectation. I’ve spent a lot of good time trying to find a good name for them but haven’t, so I’m just calling them “the third kind of expectation”. On reflection, while this is unwieldy, it is an absolutely fantastic name by the sparkly pink purple ball thing criterion.
First, a recap on the other two kinds of expectations in my model: anticipations and entitlements. An anticipation is an expectation in the predictive sense: what you think will happen, whether implicitly or explicitly. An entitlement is what you think should happen, whether implicitly or explicitly. If your anticipation is broken, you feel surprised or confused. If your entitlement is broken, you feel indignant or outraged.
I made the claim in my previous article that entitlements are in general problematic, both because they create interpersonal problems and because they’re a kind of rationalization.
Since then, some people have pointed out to me that there’s an important role that entitlements play. Or more precisely, situations where an angry response may make sense. What if someone breaks a promise? Or oversteps a boundary? It’s widely believed that an experience of passionate intensity like anger is an appropriate response to having one’s boundaries violated.
I continue to think entitlements aren’t helpful, and that what you’re mostly looking for in these situations are more shaped like this third kind of expectation.
There’s a pattern that I’ve noticed in several areas of practice, that I want to highlight. I think it’s a core piece of the challenge I’ve been writing about, around how to get out of internal conflicts. As of this sentence, I’m not totally sure why, but I’m hoping to be more sure by the time I reach the end of this post, and at minimum to have framed a question that we can look at together.
The pattern can be expressed as a simply trigger-action plan: if experiencing discomfort or challenge, orient towards it as an opportunity to practice.
The first place I recall hearing this was from Valentine at CFAR, who taught it as a central component of what was then called “againstness training”. The aim of againstness training was to develop the ability to notice one’s stress response (SNS = sympathetic nervous system activation) and be able to shift towards a more relaxed state.
One powerful step for relaxing the stress you’re encountering, he said, is to be glad for it. This doesn’t have to come first—you can go straight to a breathing exercise, but it helps if it comes first. Part of why it helps is that it provides a frame within which doing those breathing exercises makes sense! If you’re relating to stress as something to learn from, you’re going to be much more inclined to trying to work with it consciously rather than acting from it.
This “with it” rather than “from it” seems to me like a kind of subject-object shift, which suggests that maybe the role played by “being grateful for the opportunity to train” (as Val canonically phrased it) is helping you to take the stress as object. That seems like a good first analysis of it.
Is that all? Let’s look at another example, then see what becomes apparent.
Another personal learning update, this time flavored around Complice and collaboration. I wasn’t expecting this when I set out to write the post, but what’s below ended up being very much a thematic continuation on the previous learning update post (which got a lot of positive response) so if you’re digging this post you may want to jump over to that one. It’s not a prerequisite though, so you’re also free to just keep reading.
I started out working on Complice nearly four years ago, in part because I didn’t want to have to get a job and work for someone else when I graduated from university. But I’ve since learned that there’s an extent to which it wasn’t just working for people but merely working with people long-term that I found aversive. One of my growth areas over the course of the past year or so has been developing a way-of-being in working relationships that is enjoyable and effective.
I wrote last week about changing my relationship to internal conflict, which involved defusing some propensity for being self-critical. Structurally connected with that is getting better at not experiencing or expressing blame towards others either. In last week’s post I talked about how I knew I was yelling at myself but had somehow totally dissociated from the fact that that meant that I was being yelled at.
Lots of more abstract writing in the works, but in the meantime, an update on my personal learning process: I’m currently working on shifting out of a meta-oscillation between being intensely purpose-driven but stressed & tense and being self-compassionate & internally aligned but aimless & disoriented.
Of course, an update on my personal learning process is still going to include some abstractions!
I sketched out a 2×2 to capture these dimensions. I’m not totally satisfied with the axes or the quadrants, but the overall structure feels clear and powerful, and I’ll refine it over time. I’m trying to get more comfortable putting out drafts of things:
— Malcolm🌊Ocean (@Malcolm_Ocean) June 23, 2017
The ideal state is the one in the top right, » read the rest of this entry »
The process “giving feedback” is outdated. Or limited, at least.
Let’s do a post-mortem on a post-mortem, to find out why…
My friend Benjamin (who works with me on both Complice and the Upstart Collaboratory culture project) and I had an experience where we were making some nachos together, and… long story short: most of them burnt. We then spent a bit of time debriefing what had happened. What was the chain of events that led to the nachos burning? What had we each experienced? What did we notice?
This yielded a bunch of interesting and valuable observations. One thing that it did not yield was any plans or commitments for how we would do it differently in the future. Anything like “So when [this] happens next time, I’ll do [that], and that will act as a kind of preventative measure.”
Given that lack of future plans or commitments, one might ask: was it a waste of time? Did we not really learn anything? Will things just happen the same way again? » read the rest of this entry »
Much of this post was originally drafted a couple years ago, so the personal stories described in here took place then. I’m publishing it now in part because the novella that inspired it—Ted Chiang’s Story of your Life—has recently been made into a feature-length movie (Arrival). In some contexts, it might make sense to say that this post may contain spoilers for SOYL; in this particular one, that would be hilariously ironic. Even after reading this post, the story will be worth reading.
This post begins, like so many of mine, with a conversation with Jean, the founder of the Upstart Collaboratory, where she and I and others are practicing the extreme sport of human relating. Jean remarked that a conversation she’d had earlier that day had been really good, then noted that she’d already told me that.
I replied, “Well, yes, and it was meaningful to me that you said it again. On the most basic level, it implies that on some level you felt you hadn’t yet conveyed just how good the conversation had been.” Then I shared with her something I’d heard from Andrew Critch, at a CFAR workshop. (Quote is from memory)
If someone says “something” to you, then that doesn’t mean that “something” is true. It also doesn’t necessarily mean that that person believes that “something” is true. Incidentally, it also doesn’t necessarily mean that they think that you don’t already agree with them that “something”. It really just means that, at the moment they said it, it made sense to them to say “something”. To you.
I was having a lot of challenge figuring out where to start this one. For some reason, the Object/Process/Meta structure I used the past three years doesn’t feel like it makes sense this year. Maybe because this year a lot of the object-level “stuff I did” was itself process- or meta-level.
The first thing I need to get out of the way is that as of last week, I’m using the Holocene calendar, which means that instead of writing my 2016 CE review, I’m writing my 12016 HE review. It’s the same year, but I’m experimenting with living in the thirteenth millennium because (4-6 years after) the birth of Christ is a weird start time for a bunch of reasons. Better is about 12,000 years ago, around the start of human civilization. There might be a slightly more accurate year, but the nice thing about just adding 10,000 years is that it means you don’t have to do any math to convert between CE and HE: just stick a 1 on the front or take it off. This in turn means I can use it in public-facing works and while it might be a little confusing, it’s still easily-understood. Here’s a great YouTube video on the subject. I’ll tell you if/how this affects my thinking during next year’s yearly review, after I’ve been using it for awhile.
Okay, 12016. » read the rest of this entry »
I’m flexing my blogging muscle again, for the first time in nearly 2 months. It feels a bit weird, and kinda nice. The break I took also feels both weird and nice.
There’s a trope or something about blogs where half of their posts are just the author apologizing for not posting more often. This isn’t going to be one of those—instead, my absence from this space is something that I want to reflect on, in a similar manner to my normal blog posts. How does it relate to my own growth? How does it relate to motivation? To metacognition?
This reflection ends up spanning 5 years and touching on a lot of what’s core to me (and what was core in the past). » read the rest of this entry »
I realized recently that while I’m pretty consistently operating out of Growth Mindset, there’s another mindset shift that I’m often missing.
I was reading an insightful book called Influencer. One of the sections of the book describes a man with a love of chocolate, who wants to lose weight and tries to replace his chocolate-snacking habit with a carrot-snacking habit. I know the feel—chocolate is very compelling to me. From that book:
“Initially, failure signals the need for greater effort or persistence. Sometimes failure signals the need to change strategies or tactics. But failure should rarely signal that we’ll never be able to succeed and drive us to pray for serenity. For instance, you find yourself staring at a half-eaten ice cream cone in your hand. Should you conclude that you’re unable to stick with your eating plan so you might as well give up? Or should you conclude that since it’s hard to resist when you walk past the ice cream parlor on your way home from work, you should change your route? The first conclusion serves as discouraging brake on performance, whereas the second provides a corrective guide that helps refine your strategy.
The book describes the first response—concluding you can’t do it and giving up—as Fixed Mindset, and the second as Growth Mindset. They depict an overdramatic Fixed Mindset internal monologue:
“Henry wonders if he can overcome the genetic hand that he’s been dealt… has [no] self-discipline… surely he’s doomed… believes he hadn’t been born with ‘the right stuff.'” …etc.
I basically never have thoughts like that.
Which led me into the puzzle of why, if I’m consistently operating out of Growth Mindset, do I not consistently respond in that second way? That is, using each failure as a corrective guide, tweaking my path so I don’t encounter future temptations. » read the rest of this entry »
I try a lot of things. In the past I’ve forced myself to try things a certain oftenness. There was my 2014 habit-a-week project, and 2015’s #trythings beeminder.
I think I’m presently trying more interesting things, more often, but it’s coming from internal drives rather than external pressures. I reflected that I wanted a place to write about these—things in progress, things that might not work, small things… things that aren’t worth their own blog post at this phase.
So I’ve made a new page on my site! malcolmocean.com/experiments