<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PERSONA o SOCIEDAD QUE ENTREVISTO &#8211; Historia del Braille en América Latina</title>
	<atom:link href="https://historiabraille.org/author/persona-o-sociedad-que-entrevisto/feed/" rel="self" type="application/rss+xml" />
	<link>https://historiabraille.org</link>
	<description>Braille</description>
	<lastBuildDate>Thu, 12 Feb 2026 17:25:39 +0000</lastBuildDate>
	<language>es</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.4</generator>

<image>
	<url>https://historiabraille.org/wp-content/uploads/2026/02/cropped-Logo_fondo_claro_sf-32x32.png</url>
	<title>PERSONA o SOCIEDAD QUE ENTREVISTO &#8211; Historia del Braille en América Latina</title>
	<link>https://historiabraille.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Ejemplo entrevista</title>
		<link>https://historiabraille.org/how-to-lead-employees-through-technology-changes/</link>
		
		<dc:creator><![CDATA[PERSONA o SOCIEDAD QUE ENTREVISTO]]></dc:creator>
		<pubDate>Mon, 04 May 2020 16:18:34 +0000</pubDate>
				<category><![CDATA[Entrevista]]></category>
		<guid isPermaLink="false">http://ninzio.com/sanfran/?p=567</guid>

					<description><![CDATA[Resumen de la vista previa (corto). <a class="continue" href="https://historiabraille.org/how-to-lead-employees-through-technology-changes/">Seguir leyendo<span> Ejemplo entrevista</span></a>]]></description>
										<content:encoded><![CDATA[<div class="wpb-content-wrapper"><div class="vc_row wpb_row vc_row-fluid vc_custom_1770908484407 vc_row-o-content-middle vc_row-flex position-relative has-canvas"><div class="wpb_column vc_column_container vc_col-sm-12"><div class="vc_column-inner"><div class="wpb_wrapper"><div class="vc_message_box vc_message_box-standard vc_message_box-rounded vc_color-info vc_custom_1770917101058 vc_do_message" ><div class="vc_message_box-icon"><i class="fa fa-solid fa-user-astronaut"></i></div><h3 style="font-size: 20px;"><strong>Nombre del entrevistado</strong></h3>
</div></div></div></div></div><div class="vc_row wpb_row vc_row-fluid position-relative has-canvas"><div class="wpb_column vc_column_container vc_col-sm-12"><div class="vc_column-inner"><div class="wpb_wrapper">
	<div class="wpb_text_column wpb_content_element" >
		<div class="wpb_wrapper">
			<p>Technology is now integrated into almost every part of our jobs. We use computers, Wi-Fi, email, applications or our smartphones for everything. The thing about technology, though, is that it’s always changing. Software and programs are constantly updating, becoming better versions of themselves. New hardware is constantly outdating older laptop and desktop versions, and new applications are being developed every day.</p>
<p>To help lead employees through changes to the technology they use for work every day — and to empower each team member to succeed — consider these five steps.</p>

		</div>
	</div>
<div class="deeper-spacer clearfix" data-config='{"desktop":45,"mobile":45,"smobile":45}'></div>
	<div class="wpb_text_column wpb_content_element" >
		<div class="wpb_wrapper">
			<h6>1. Give The ‘Why’</h6>
<p>No one likes just being told what to do (OK, maybe some people enjoy that, but most employees don’t). Instead of bossing around, try giving the full picture. Explain why the change ahead is important. Explain what exactly the new technology will help with. How will it impact your overall efficiency? How will technology changes affect other parts of the processes?</p>

		</div>
	</div>
<div class="deeper-spacer clearfix" data-config='{"desktop":45,"mobile":45,"smobile":45}'></div>
	<div class="wpb_text_column wpb_content_element" >
		<div class="wpb_wrapper">
			<h6>2. Be Transparent Open communication is everything.</h6>
<p>Give your employees an overview of the process and what specific changes will be made. Have a meeting that provides a clear outline of what they can expect. If employees are already feeling anxious or overwhelmed, surprises or unexpected changes will only add to their stress. Be as transparent as possible with your team members throughout the change process.</p>

		</div>
	</div>
<div class="deeper-spacer clearfix" data-config='{"desktop":45,"mobile":45,"smobile":45}'></div>
	<div class="wpb_text_column wpb_content_element" >
		<div class="wpb_wrapper">
			<h6>3. Provide A Timeline</h6>
<p>If you have a timeline or road map for the technology changes you’re making, share that with your team. There’s going to be a learning curve for everyone, and it will be steeper for some than for others. As a leader, you can’t expect everyone to learn this new skill or new technology at the same pace. If you are able to, provide time for the new process to be implemented in a transition phase where the old process can still be used if they get stuck.</p>

		</div>
	</div>
<div class="deeper-spacer clearfix" data-config='{"desktop":45,"mobile":45,"smobile":45}'></div></div></div></div></div>
</div>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
