SPEAKER_09 41:46–44:02
So, this is all process. All we're talking about here is process. You understand the mechanics of what you're going to create potentially. And then it's like, okay, how far do they move when you intervene? And that's the question you're asking. So you don't know. You do something and then you say, okay, that's in the favorable direction. I will do a little bit more of that. And then I will monitor that change and make sure it's still trending in the right direction, right? And then you're communicating with them. If we're talking about symptom relief and things like that, that's going to be something that you would monitor as well. And that might give you the answer that you're looking for in terms of how much do I need to bring you back? So, somebody reports a reduction of symptoms but not resolution, then you probably did something that's favorable in regards to creating adaptability. Maybe you didn't create enough, maybe you didn't create enough in the right direction. So, in those weird cases where you do something with an intention, like let's just say you were trying to create ER space and maybe you moved them a little bit in that direction, but you picked up a ton of IR and they go, oh, that feels better, but in your head, you're going, okay, but that wasn't what I was really trying to do. So you created more adaptability, so you expanded the excursion that they can move through, but you didn't access the starting position into ER that you wanted. So again, that symptom relief versus the performance aspect of it that was your original intention, you still have to test. So it's always intervention and then reassess, and then intervention and reassess, intervention reassess. Because again, the questions that you're asking are great questions, but they are resolved in process. Because your predictive capabilities are slim.
process-driven interventionadaptabilitysymptom reliefreassessmentpredictive capabilities