Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::hasChildren($allow_links = true) should either be compatible with RecursiveDirectoryIterator::hasChildren(bool $allowLinks = false): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 57

Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::rewind() should either be compatible with FilesystemIterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 35

Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::next() should either be compatible with DirectoryIterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 42

Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 47

Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 37

Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 41

Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 37

Deprecated: Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/scpnlcl/public_html/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-newline-filter.php on line 28

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the blocksy-companion domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the check-email domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the essential-blocks domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the spiffy-calendar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultimate-addons-for-gutenberg domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the blocksy domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the blocksy domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121

Notice: La función _load_textdomain_just_in_time ha sido llamada de forma incorrecta. La carga de la traducción para el dominio blocksy se activó demasiado pronto. Esto suele ser un indicador de que algún código del plugin o tema se ejecuta demasiado pronto. Las traducciones deberían cargarse en la acción init o más tarde. Por favor revisa Depurando en WordPress para más información. (Este mensaje se añadió en la versión 6.7.0.) in /home/scpnlcl/public_html/wp-includes/functions.php on line 6121
El Entrenamiento para Practitioner en PNL – Sociedad Chilena de Programación Neuro-lingüística

El Entrenamiento para
Practitioner en PNL

Con frecuencia personas me preguntan sobre el Entrenamiento para Practitioner en PNL. Antiguamente me preguntaban ¿qué es la PNL? Pero ahora hay suficientes libros y artículos describiéndola que esa pregunta ya se disipó bastante. La pregunta sobre el Practitioner aún persiste… y es muy válida.  

Tal vez no sea quien deba dar una respuesta definitiva a esa pregunta… tal vez tal respuesta absoluta no exista… o por lo menos no perdure en el tiempo. Independientemente, le daré mi ángulo al tema y espero con el, satisfacer algunas inquietudes que sé que existen “por allí”. Para empezar, entendamos la palabra Practitioner (pronunciada “Prac-ti-sho-ner”). Ella, en inglés significa Practicante. Esto se le designa a quién ejerce o practica (valga la redundancia) alguna actividad.  

Entonces el Entrenamiento para Practitioner es un entrenamiento para prepararte como futuro Practicante del arte y técnicas de la PNL.  

Diferentes escuelas de PNL incluyen diferentes materiales y ejercicios. Esto cada una lo hace según su criterio. No entraré en lo que considero debe ser el criterio de selección de material y ejercicios de cada uno. Si diré que a nosotros en la SCPNL nos gusta una buena mezcla de todo lo que consideramos altamente efectivo.  

El Entrenamiento para Practitioner en PNL debe, en unas 125 a 150 horas de clases presénciales y otras 20 a 40 horas de estudio y ejercicio individual, lograr tornar al alumno en un principiante funcional. Un principiante capaz de otorgar un buen servicio y de perfeccionar su arte con la práctica.  

Esto quiere decir que, en relación a temas emocionales, conductuales y comunicacionales, el Practitioner en PNL recién titulado, debiera poder definir el Estado Actual del asunto a tratar, su génesis y contextos de activación, el Estado Deseado funcional y “ecológico” del mismo asunto y, usando las técnicas disponibles en su manual, generar el cambio de forma respetuosa y duradera para su cliente.  

Eso es un Entrenamiento para Practitioner en PNL… es un entrenamiento que capacita para aplicar de forma efectiva y cada vez mejor la PNL en uno mismo y en otros.       También el Practitioner es el primer nivel formativo de la PNL, el que lo sigue es el de Master Practitioner (Practicante con Maestría) y después viene el de Trainer (Entrenador/Capacitador).  

Espero que esto aclare el tema del Practitioner

Alan Frenk
Fundador Sociedad Chilena de Programación Neuro-Lingüística.

💬 Alguna consulta?