To address the actual point of the OP's thread, rather than the conversation since:
You can utilize what we do know about RV (the psi part), regardless of (a) not knowing everything about how to utilize it, and (b) not knowing everything about how to perform it and (c) not knowing "why" or "how" it works.
It's important to work in an "engineer, not scientist" model as a viewer because the real question is not "how does it work" or "why does it work" but rather "does it work?" Engineers will build stuff just to see, even crazy unlikely things; unlike most scientists, they don't need an armchair theory their psychology feels good about and safe with, in order to actually just DO something and "see what happens". That's an important state of mind and approach to remote viewing, because it IS so unknown on so many levels, and because even what is known thanks to science, it is still a totally new experience for each person diving into it.
As an example, you can take a given problem in the real world that you have some ability to apply possible solutions to. And then, you can look at what at least some viewers can do sometimes, and brainstorm, "How can I task this to ask a specific question, that if I got the answer I would recognize it, and I could find a way to apply that knowledge to good effect?" (Strangely this is not at all as easy as it sounds, especially the latter two points.) Sometimes it takes trial and error. Sometimes it takes finding different viewers. (Not necessarily better, but perhaps with different strengths.) Sometimes it takes tasking differently.
In any case, it is always going to require some intelligent thought and working out how what RV can do--that includes understanding its limitations and its issues--and how that could best be applied to a given situation.
For example let's say you know something is going to happen but have no idea of the date. You could task the viewer on a timeline (forced-choice data) or calendar (abstracted data); they may or may not be accurate or useful. You can task the viewer in a free-response format (which is more literally RV) and hope they tell you when it happens as that's the task, and if they don't, retask them a few times till they do, and if they don't, either task it differently, task a different viewer, or give up. You could task the viewer to describe the concepts and experience related to the "major holiday which happens nearest the event" and then try to narrow in from that point (assuming you figure out the data means 'christmas' and not 'memorial day'). You could task the viewer to describe the weather and the trees on the day of the event and see if you get a seasonal idea.
This is a rather simplistic example off the top of my head (there are probably better examples), but what I am trying to demonstrate is that even if you want a kind of data that psychic functioning does not very well provide (accurately), you can usually find a way to "task around" it until you get to some kind of data that RV *does* do ok with.
Along the way you might discover that the process--or a certain viewer--provides you by surprise exactly what you need by 'chance'.
Along the way you might have to task things repeatedly, or task pieces of something multiple times to get more info, or task differently, or task a different viewer. Psi is not predictable, not per team, per viewer, per target, or per session.
You might also discover that what the tasker has in mind has the potential to affect the data, that the feedback given the viewer has the potential to affect the data, and that there is a huger need for 'clean protocol' -- and this is mental and affects everyone part of the effort -- than most people realize. So there is plenty for taskers to learn as well.
Anyway. So my point is that no matter how ignorant we may still be about psychic functioning and the 'why and how', one CAN, still, work toward applying it practically. Everything we learn does improve our ability to 'use' it -- certainly! But just because it is fairly new to be 'practically' used, does not mean it's impossible to do so.
RC
You can utilize what we do know about RV (the psi part), regardless of (a) not knowing everything about how to utilize it, and (b) not knowing everything about how to perform it and (c) not knowing "why" or "how" it works.
It's important to work in an "engineer, not scientist" model as a viewer because the real question is not "how does it work" or "why does it work" but rather "does it work?" Engineers will build stuff just to see, even crazy unlikely things; unlike most scientists, they don't need an armchair theory their psychology feels good about and safe with, in order to actually just DO something and "see what happens". That's an important state of mind and approach to remote viewing, because it IS so unknown on so many levels, and because even what is known thanks to science, it is still a totally new experience for each person diving into it.
As an example, you can take a given problem in the real world that you have some ability to apply possible solutions to. And then, you can look at what at least some viewers can do sometimes, and brainstorm, "How can I task this to ask a specific question, that if I got the answer I would recognize it, and I could find a way to apply that knowledge to good effect?" (Strangely this is not at all as easy as it sounds, especially the latter two points.) Sometimes it takes trial and error. Sometimes it takes finding different viewers. (Not necessarily better, but perhaps with different strengths.) Sometimes it takes tasking differently.
In any case, it is always going to require some intelligent thought and working out how what RV can do--that includes understanding its limitations and its issues--and how that could best be applied to a given situation.
For example let's say you know something is going to happen but have no idea of the date. You could task the viewer on a timeline (forced-choice data) or calendar (abstracted data); they may or may not be accurate or useful. You can task the viewer in a free-response format (which is more literally RV) and hope they tell you when it happens as that's the task, and if they don't, retask them a few times till they do, and if they don't, either task it differently, task a different viewer, or give up. You could task the viewer to describe the concepts and experience related to the "major holiday which happens nearest the event" and then try to narrow in from that point (assuming you figure out the data means 'christmas' and not 'memorial day'). You could task the viewer to describe the weather and the trees on the day of the event and see if you get a seasonal idea.
This is a rather simplistic example off the top of my head (there are probably better examples), but what I am trying to demonstrate is that even if you want a kind of data that psychic functioning does not very well provide (accurately), you can usually find a way to "task around" it until you get to some kind of data that RV *does* do ok with.
Along the way you might discover that the process--or a certain viewer--provides you by surprise exactly what you need by 'chance'.
Along the way you might have to task things repeatedly, or task pieces of something multiple times to get more info, or task differently, or task a different viewer. Psi is not predictable, not per team, per viewer, per target, or per session.
You might also discover that what the tasker has in mind has the potential to affect the data, that the feedback given the viewer has the potential to affect the data, and that there is a huger need for 'clean protocol' -- and this is mental and affects everyone part of the effort -- than most people realize. So there is plenty for taskers to learn as well.
Anyway. So my point is that no matter how ignorant we may still be about psychic functioning and the 'why and how', one CAN, still, work toward applying it practically. Everything we learn does improve our ability to 'use' it -- certainly! But just because it is fairly new to be 'practically' used, does not mean it's impossible to do so.
RC