<?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>Social Media Writing for Smart People &#187; cv</title>
	<atom:link href="http://www.ivanwalsh.com/tag/cv/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ivanwalsh.com</link>
	<description>Get smart with better social media writing skills</description>
	<lastBuildDate>Sat, 05 Nov 2011 17:15:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Why Your About Us Page is the Second Most Important Page on Your Site?</title>
		<link>http://www.ivanwalsh.com/google-tips/wordpress-about-us-google-pagerank-tips/</link>
		<comments>http://www.ivanwalsh.com/google-tips/wordpress-about-us-google-pagerank-tips/#comments</comments>
		<pubDate>Thu, 18 Mar 2010 04:34:08 +0000</pubDate>
		<dc:creator>Ivan</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[About Us]]></category>
		<category><![CDATA[brand]]></category>
		<category><![CDATA[Conference]]></category>
		<category><![CDATA[Contact Form]]></category>
		<category><![CDATA[Conversion]]></category>
		<category><![CDATA[Convert]]></category>
		<category><![CDATA[customers]]></category>
		<category><![CDATA[cv]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[Page Rank]]></category>
		<category><![CDATA[Portfolio]]></category>
		<category><![CDATA[Prospects]]></category>
		<category><![CDATA[rates]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.ivanwalsh.com/?p=4199</guid>
		<description><![CDATA[<a href="http://www.ivanwalsh.com/google-tips/wordpress-about-us-google-pagerank-tips/"><img align="left" hspace="5" width="50" src="http://www.ivanwalsh.com/wp-content/uploads/2010/03/youtube-videos-about-us-tips.jpg" class="alignleft wp-post-image tfe" alt="" title="youtube-videos-about-us-tips" /></a>You find a blog you really like. You want to learn more. You're thinking of buying from them. What do you do? Click About Us, right? Most people do. Now, pretend you’ve never visited your own site. Remember, you know nothing about you. Nothing. Look at your About Us page? Be honest, what’s the one thing that’s wrong with it?]]></description>
			<content:encoded><![CDATA[<p></p><p><a href="http://www.ivanwalsh.com/wp-content/uploads/2010/03/youtube-videos-about-us-tips.jpg"><img class="alignleft size-full wp-image-4204" title="youtube-videos-about-us-tips" src="http://www.ivanwalsh.com/wp-content/uploads/2010/03/youtube-videos-about-us-tips.jpg" alt="" width="101" height="58" /></a>You find a blog you really like. You want to learn more. You&#8217;re thinking of buying from them. What do you do? Click About Us, right? Most people do. Now, pretend you’ve never visited your own site. Remember, you know nothing about you. Nothing. Look at your About Us page? Be honest, what’s the one thing that’s wrong with it?<span id="more-4199"></span></p>
<h3>Why Your About Us Page is the Second Most Important Page on Your Blog?</h3>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="344" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/xg_KdnFFvEo&amp;hl=en_US&amp;fs=1&amp;" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="425" height="344" src="http://www.youtube.com/v/xg_KdnFFvEo&amp;hl=en_US&amp;fs=1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<p>Video made at The Temple of Heaven, China during soccer practice &#8230;</p>
<p>Your About Page should NOT be:</p>
<ul>
<li><strong>An Afterthought</strong> – something to fill with text, just to get it done. Written after the site is launched when you’ve nothing else to do on a slow Friday afternoon.</li>
<li><strong>In the third person</strong> — it’s your blog! Talk to me. Introduce who you are. Don’t talk down. Talk about your team, mention their names, show their faces, add pic and videos. Why not?</li>
<li><strong>Flat</strong> — read the first paragraph. Does it excite you? Does it make ‘you’ (i.e. the prospect) want to contact you, download your brochure, make an effort to connect?</li>
<li><strong>Same</strong> <strong>As</strong>— as every other About Us page. C’mon, you can do better. Pics, videos and mp3s. it’s so easy, try it.</li>
<li><strong>Stale</strong> — update it every 3 months. Every month you do something worth sharing. Put it here.</li>
</ul>
<p>Your About Page should be:</p>
<ul>
<li><strong>Kinda Intimate</strong> – share something that cannot be found anywhere else on the site. Photos, videos, examples of your portfolio, places you’ve been, events, conferences — anything that paints a picture.</li>
<li><strong>But Warm</strong> – make me feel ‘warm and fuzzy’ inside. You don’t need to go over-board, but <a href="http://www.ivanwalsh.com/how-to/20-mistakes-i-made-when-making-it-to-2-on-google/1093/">share a little</a>. Show why you&#8217;re more interesting that the rest.</li>
<li><strong>With 7 Compelling Reasons</strong> — give them 7 reasons (if you can’t think of seven, at least five) to cross the threshold and connect. For example, what do you stand for? What are your values? Who have you helped? What charity do you support? What makes you different (really different!) than the rest.</li>
<li><strong>For them to Knock on the Door </strong>– remember, it’s this page where people decide ‘will I, won’t I?’ So, it better be good. You want them to come in, right?</li>
</ul>
<h3>How To Sharpen Your About Us page</h3>
<p>Your About Us page must have the following:</p>
<ul>
<li>Story – not your CV, <a href="http://www.ivanwalsh.com/lifestyle/10-cities-visit-lifestyle-travel-must-see/4165/">but the story of YOU</a>.</li>
<li>Why did you decide to do this?</li>
<li>How did you get here?</li>
<li>What <a href="http://www.ivanwalsh.com/technical-writing/10-best-mistakes-i-made-in-2009/3775/">mistakes did you make</a>?</li>
<li>What you hope to achieve?</li>
<li>Why the reader is important to you?</li>
<li>Share links to your Social Media sites</li>
<li>Contact form  &amp; email &amp; tel number —make it easy for them. Put your contact details on every page.</li>
</ul>
<h3>Videos and Personal Branding</h3>
<p>I use <a href="http://www.youtube.com/ivanwalsh">videos to help bridge that gap</a>. You see me at work, at soccer practice, with junior, <a href="http://www.flickr.com/photos/ivanwalsh/4428645516/">my pet crickets</a>, and even when I’m struggling. Each of these helps close the gap between you and me. Maybe you don’t care for everything on the site, but your impression of me (and your memories of this site) are that much stronger.</p>
<p><strong>Here’s a question for you?</strong></p>
<p>Think of all the sites you visited this week. How many do you remember? Now, look at the video above. In a year’s time, you will still remember this video (for better or worse!) but all the blogs you read this week will be forgotten.</p>
<p>Why do you think that is?</p>
<p><strong>PS</strong> &#8211; Rewriting your About Us page could result in a higher Google page rank and higher conversion rates for those who find it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ivanwalsh.com/google-tips/wordpress-about-us-google-pagerank-tips/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>5 Tips on How to Make a Cold Call and Survive!</title>
		<link>http://www.ivanwalsh.com/how-to/5-tips-on-how-to-make-a-cold-call-and-survive/</link>
		<comments>http://www.ivanwalsh.com/how-to/5-tips-on-how-to-make-a-cold-call-and-survive/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 01:35:25 +0000</pubDate>
		<dc:creator>Ivan</dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[Adobe Framemaker]]></category>
		<category><![CDATA[Career]]></category>
		<category><![CDATA[cv]]></category>
		<category><![CDATA[tech docs]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[whitesmoke]]></category>
		<category><![CDATA[writing software]]></category>

		<guid isPermaLink="false">http://www.ivanwalsh.com/?p=1652</guid>
		<description><![CDATA[<a href="http://www.ivanwalsh.com/how-to/5-tips-on-how-to-make-a-cold-call-and-survive/"><img align="left" hspace="5" width="50" height="50" src="http://www.ivanwalsh.com/wp-content/plugins/thumbnail-for-excerpts/tfe_no_thumb.png" class="alignleft wp-post-image tfe" alt="" title="" /></a>5 Tips on How to Make a Cold Call and Survive!]]></description>
			<content:encoded><![CDATA[<p></p><p>Cold calls! No! I can’t do it. Yes, you can. They’re only human and won’t bite.</p>
<p><strong>Here’s how I make cold calls and it works</strong></p>
<p>When I started out I hated this. I’d do anything to avoid it. In the end I cut a deal with myself. I would call between 10-11 every morning for 1 hour and 1 hour only. Somehow this worked. I’d make the calls and get it over with. In time it got easier and making cold calls became more enjoyable. Yes, imagine that. Cold calls that you enjoy!<span id="more-1652"></span></p>
<p>[ad]</p>
<p><strong>Before you make your first cold call</strong></p>
<p>Before you make the call, look at their site, download their brochures and see what type of documents they might need. For example, software development companies may need user guides, release notes, and installation manuals.</p>
<p>Web companies will need online text, technical support material and help pages. After a while you’ll get a feel for what these companies want and you can tailor your cold calls accordingly.</p>
<p>Don’t be shy about calling. Expect to get turned down 9 out of 10 times at first. It’s nothing personal. And don’t be hard on yourself. Starting up is the hardest part. Once you land your first contract, the next will be much easier.</p>
<div></div>
<p>1.	Start with small companies that don’t have dedicated in-house tech writers.</p>
<p>2.	Don’t contact the HR Manager. Their job is to screen you out. They won’t be interested.</p>
<p>3. Contact the IT Manager or the Training Manager. These people may actually need your skills. Drop them an email and ask if you can send over a brochure. No hard selling. Gently does it</p>
<p>4.	Offer your services on a contract basis</p>
<p>5.	If asked, give them estimates of your daily rates &#8211; but keep it general.</p>
<p>6.	Avoid getting locked into low rates before you have met the client.</p>
<p><strong>Tip</strong>: This is a numbers game. The more you call, the more interviews you’ll get. It’s not rocket science. Just persevere.</p>
<p>Remember the words of Churchill: “Never, Never, Never give up.”</p>
<p><strong><br />
</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ivanwalsh.com/how-to/5-tips-on-how-to-make-a-cold-call-and-survive/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Interview Technical Writers</title>
		<link>http://www.ivanwalsh.com/how-to/how-to-interview-technical-writers-2/</link>
		<comments>http://www.ivanwalsh.com/how-to/how-to-interview-technical-writers-2/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 02:09:39 +0000</pubDate>
		<dc:creator>Ivan</dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[Adobe Captivate]]></category>
		<category><![CDATA[Adobe Framemaker]]></category>
		<category><![CDATA[Adobe FrameMaker]]></category>
		<category><![CDATA[Adobe Technical Communication Suite]]></category>
		<category><![CDATA[Career]]></category>
		<category><![CDATA[cv]]></category>
		<category><![CDATA[DITA Open Toolkit]]></category>
		<category><![CDATA[Long Documents]]></category>
		<category><![CDATA[Robohelp]]></category>
		<category><![CDATA[salary]]></category>
		<category><![CDATA[technical communicators]]></category>
		<category><![CDATA[Technical documentation]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[Templates]]></category>

		<guid isPermaLink="false">http://www.ivanwalsh.com/?p=1488</guid>
		<description><![CDATA[<a href="http://www.ivanwalsh.com/how-to/how-to-interview-technical-writers-2/"><img align="left" hspace="5" width="50" src="http://www.klariti.com/Technical-Writing-Tests/technical-writing-tests.gif" class="alignleft wp-post-image tfe" alt="" title="" /></a>Here are some tips for interviewing technical writers, for example, if your company needs to hire a contractor to write some documentation for your next release.]]></description>
			<content:encoded><![CDATA[<p></p><p><a href="http://www.klariti.com/Technical-Writing-Tests/index.shtml" target="_blank"><img class="alignright" src="http://www.klariti.com/Technical-Writing-Tests/technical-writing-tests.gif" alt="" width="150" height="195" /></a> Here are some tips for interviewing technical writers, for example, if your company needs to hire a contractor to write some documentation for your next release.</p>
<p>I’ve worked on both sides on the fence, (i.e. went to lots of interviews and also interviewed applicants for roles our Publications Dept) and picked up a few things in the process.</p>
<p>Hopefully, these will be of some help.<span id="more-1488"></span></p>
<p>[ad]</p>
<p class="MsoNormal">A Technical Writer is someone how writes technical documentation for a piece of software, for example, a <a href="http://www.klariti.com/user-guide/index.shtml">User Guide or a System Administration Manual</a>.</p>
<p class="MsoNormal">They are responsible for writing text that is accurate, readable, accessible, and helpful to its intended audience.</p>
<div><strong>1.  How to test Writing Skills</strong></div>
<p class="MsoNormal"><span lang="EN-US">Most companies use assessment tests to determine the skill level of potential employees.</span></p>
<p class="MsoNormal" style="text-align: center;"><img class="size-full wp-image-1489 aligncenter" title="shi2" src="http://www.ivanwalsh.com/wp-content/uploads/2009/06/shi2.jpg" alt="shi2" width="333" height="227" /></p>
<p class="MsoNormal">Download Technical Writer Assessment Tests here:</p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://www.klariti.com/Technical-Writing-Tests/index.shtml">http://www.klariti.com/Technical-Writing-Tests/index.shtml</a></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://www.klariti.com/Technical-Writing-Tests/index.shtml"></a><strong>How much time should be allotted to complete an assessment test?</strong></span></p>
<p class="MsoNormal"><span lang="EN-US">I’d suggest 1 hour at most. 45 min should be enough. </span></p>
<p class="MsoNormal"><span lang="EN-US">More experienced writers will race through it, while others might deliberate over those tricky questions until absolutely sure. </span></p>
<p class="MsoNormal"><span lang="EN-US">Nonetheless, 1 hour should be sufficient time for most to complete the test.</span></p>
<p class="MsoNormal"><span lang="EN-US">Also, by allocating this amount of time to the test, you are also <strong>emphasizing its relative importance</strong>. If it were a simple 10-minute quiz, it wouldn’t carry the same weight.</span></p>
<p class="MsoNormal"><span lang="EN-US">Here’s a suggested approach for administering the test:</span></p>
<p class="MsoNormal"><span lang="EN-US">When advertising the vacancy, highlight that an evaluation test is part of the assessment process. By saying this upfront, you weed out under-qualified writers who know that they would not pass the test.</span></p>
<p class="MsoNormal"><span lang="EN-US">When scheduling the interview, remind applicants of the assessment test and to ensure that they arrive on time. </span></p>
<p class="MsoNormal"><span lang="EN-US">1. Explain to them what is involved, for example, that there is X number of questions on grammar, procurement, technology etc. This demonstrates your company’s professionalism as you are helping the applicants to prepare for the interview. In turn, it would be unprofessional to spring the test on applicants when they turn up and catch them by surprise.</span></p>
<p class="MsoNormal"><span lang="EN-US">2. Completing the test take about 90 minutes and some of your applicants may have other arrangements to consider, such as day-care, commuting etc.</span></p>
<p class="MsoNormal"><span lang="EN-US">3. When they arrive, <strong>interview them first and then do the test.</strong> If they are unsuitable for the position, you can cancel the test and say that it’s not necessary at this point. </span></p>
<p class="MsoNormal"><span lang="EN-US">In the interview ask them about: </span></p>
<ul>
<li>Technical Writing software they have use and which products they prefer to use.</li>
<li>Note if they have a preference/bias towards a specific platform</li>
<li>Ask why they prefer one Technical Writing tool over another, for example, why do they prefer <a href="http://www.ivanwalsh.com/2009/05/response-to-is-madcap-flare-a-better-tool-than-robohelp/">Adobe RoboHelp over MadCap Flare</a>?</li>
<li>Ask for examples of how they solved problems. This helps get a handle on how they interact with other members of the Technical Publication Dept.</li>
</ul>
<p>About.com has some sample questions for holding interviews:</p>
<p>http://humanresources.about.com</p>
<p><strong>Different Types of Questions</strong></p>
<p>Use different types of questions when interviewing prospective employees.</p>
<ul>
<li>Behaviors &#8211; about what the person has done or is doing</li>
<li>Opinions &#8211; about what they think about a topic, for example, the rise in video as a tool for technical communications</li>
<li>Knowledge – ask specific questions to get facts, for example, <a href="http://www.ivanwalsh.com/2009/05/mapping-of-pdf-annotations-to-framemaker-9-comments/">what version of Adobe FrameMaker</a> do you use?</li>
<li>Background/demographics – ask standard background questions, such as education, training to develop a profile of the applicant and also to cross-check their resume</li>
</ul>
<p><strong>Sequence of Questions</strong></p>
<ul>
<li>Ask questions about some facts. This approach encourages respondents to relax and engage in the interview.</li>
<li>Ask questions about the present first.</li>
<li>Then discuss the past or future. It&#8217;s easier to talk about the present and then work into the past or future.</li>
<li>Close by allowing respondents to provide other information they prefer to add and also give their impressions of the interview. More assertive types will have suggestions/opinions and express themselves more confidently.</li>
</ul>
<p><strong>Wording of Questions</strong></p>
<ul>
<li>Use open-ended questions.</li>
<li>Avoid Yes/No questions. Let the applicants choose their own terms when answering questions.</li>
<li>Stay neutral. Avoid wording questions that might influence their answers, e.g. showing a prejudice towards a specific platform or development environment.</li>
<li>Ask questions one at a time.</li>
<li>Be careful asking &#8220;why&#8221; questions as this may make the person to feel defensive, e.g., have to justify their response/feelings.</li>
</ul>
<p><strong>Conducting the Interview</strong></p>
<ul>
<li>Ask one question at a time.</li>
<li>Remain as neutral as possible. Avoid showing strong emotional reactions to their responses.</li>
<li>Encourage responses with occasional nods of the head, &#8220;uh huh&#8221;s, etc.</li>
<li>Be careful when taking notes. For example, if you start to write feverishly, it may appear as if you&#8217;re shocked with the answer, which is likely to influence the following answers. Likewise, if you stop taking notes it implies that you’ve lost interest.</li>
<li>Move from topics to topic, e.g., &#8220;ok, we&#8217;ve been talking about Adobe FrameMaker and now I&#8217;d like to move on to Structured Authoring.&#8221;</li>
<li>Remain in control of the interview. Stop respondents from straying to other topics, rambling, or turning the tables on the interviewer.</li>
</ul>
<p><strong>Starting the Written Assessment</strong></p>
<p>For those you want to assess, do the following:</p>
<ul>
<li>Give them a pen and paper (always helps). Some people like to sketch or keep notes when writing.</li>
<li>Glass of water or coffee.</li>
<li>Find a quiet room with a PC or laptop.</li>
<li>Give them a printout of the test. Hardcopies are often easier to read than words on the screen.</li>
<li>Walk through the test so that they understand what is required.</li>
<li><strong>Encourage them to ask any questions so there are no misunderstandings</strong>.</li>
<li>Tip: Remind them when the test will finish.</li>
<li>Once they are ready, leave the room and let them do the test.</li>
<li>After 20 minutes, drop in to see how they are doing. The point here is not to monitor them, but to see if they genuinely need any assistance.</li>
<li>After 60 minutes return, stop the test, and print it out.</li>
</ul>
<p>At this point, I d suggest that they have a break so that you can score the test or let them know that you will call them tomorrow with the result.</p>
<p>This may be the <strong>most practical approach if you plan to hold a second interview</strong>.</p>
<p>If you want to do it the same day, then get the printout and go over the scores. As everyone likes to know how they performed in a test, walk through the results and discuss them with the applicant.</p>
<p>For example, <strong>if they scored low in one section, ask them how this area could be improved</strong>.</p>
<p>Finally, thank them for taking the time to do the tests and hope that they have gained from it.</p>
<p><strong>Download <a style="text-decoration: none;" href="http://www.klariti.com/Technical-Writing-Tests/index.shtml">Technical Writer Assessment Tests</a></strong></p>
<p class="MsoNormal"><span lang="EN-US"><img class="aligncenter" src="http://www.klariti.com/Technical-Writing-Tests/technical-writing-tests.gif" alt="" width="150" height="195" /></span></p>
<p class="MsoNormal"><span lang="EN-US">Full URL: <a style="text-decoration: none;" href="http://www.klariti.com/Technical-Writing-Tests/index.shtml">www.klariti.com/Technical-Writing-Tests/index.shtml</a></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.ivanwalsh.com/how-to/how-to-interview-technical-writers-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

