<?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>Karen &#8211; Spark Content</title>
	<atom:link href="https://sparkcontent.ca/tag/karen/feed/" rel="self" type="application/rss+xml" />
	<link>https://sparkcontent.ca</link>
	<description></description>
	<lastBuildDate>Fri, 20 Apr 2018 16:17:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.3</generator>
	<item>
		<title>Happy Birthday Spark Content!</title>
		<link>https://sparkcontent.ca/2016/03/08/happy-birthday-spark-content/</link>
		
		<dc:creator><![CDATA[KMoProAVD]]></dc:creator>
		<pubDate>Tue, 08 Mar 2016 20:06:30 +0000</pubDate>
				<category><![CDATA[Writing]]></category>
		<category><![CDATA[Angela]]></category>
		<category><![CDATA[Karen]]></category>
		<category><![CDATA[Tracy]]></category>
		<guid isPermaLink="false">http://sparkcontent.ca/?p=351</guid>

					<description><![CDATA[We’ve worked together for years, but we were still excited to celebrate Spark&#8217;s one-year anniversary recently. Although, we almost missed it because we were so busy! To mark the occasion, we celebrated with a team lunch, taking a few minutes .....]]></description>
										<content:encoded><![CDATA[<p>We’ve worked together for years, but we were still excited to celebrate Spark&#8217;s one-year anniversary recently. Although, we almost missed it because we were so busy!</p>
<p>To mark the occasion, we celebrated with a team lunch, taking a few minutes to think about what we’ve learned over the last year and make a resolution for the year to come.</p>
<h4>1. Don’t panic when all of the projects come in at once!</h4>
<p>As contractors, we are at the mercy of other people’s timelines. We can sketch out a project schedule that fits perfectly around our other projects, but if one deadline slips by a few weeks, the domino effect that it can have can wreak havoc with our stress levels.</p>
<p>But, we’ve learned to breathe. We remind ourselves that, with three of us, we’ve got this. We&#8217;re expert planners and have years of experience juggling projects and working to timelines. After all, our ability to load-balance between the three of us is one of the benefits of hiring us!</p>
<h4>2. Not all business relationships are about drumming up business.</h4>
<p>We had a great time chatting with people at September’s Communitech TechJam. We knew that most companies were looking for developers, not writers, but many companies were happy to talk with us, too. That&#8217;s what&#8217;s so great about the Waterloo tech community: everyone is supportive of local businesses, no matter what your talent is. We learned more about some of local tech companies and made some great connections. And, if those connections bring work in the future, we&#8217;ll consider that a bonus.</p>
<p>Outside of the tech community, we found that the small business community is just as supportive as the tech community. We sincerely enjoy the weekly WRTalk Twitter chats and the quarterly in-person meetups, where we find out more about the amazing small businesses in Waterloo Region. Without those connections, we wouldn&#8217;t have discovered businesses such as <a href="http://www.shawermaplus.com/" target="_blank" rel="noopener noreferrer">Shawerma Plus</a> supporting Syrian refugees – not to mention discovering their awesome shawarma!</p>
<p>We’ve also connected with professionals in the area who can enhance what we do. When you work for a big company, it&#8217;s easy to insulate yourself within it. When you’re a contractor, there’s nowhere to hide. But there are a number of fabulous marketing, UX, and graphic design professionals in K-W. We&#8217;ve learned that it&#8217;s helpful to have a network that you can trust if work comes up that doesn&#8217;t fall within your area of expertise.</p>
<h4>3. Know when to say no to an opportunity that isn&#8217;t right.</h4>
<p>We love what we do and with our experience and knowledge, we know that we can help our clients. Sometimes, however, the best way to help them is to say no. That might mean saying no to the first request, but after further discussion, uncovering what they really need. We’re very good at asking questions. And, with the right questions, we can find out what the client is really trying to achieve and guide them towards a solution that will meet that need.</p>
<p>Rarely, saying no means saying goodbye to a potential client and pointing them in the direction of someone who is more in line with what they are looking for. But, it can happen, and we’ve learned that it isn’t the end of the world. It’s another reason to have that network of excellent contacts to point people to. It&#8217;s better to have a good relationship with a contact than a bad relationship with a client.</p>
<h4>Our resolution: keep the awesome coming</h4>
<p>We&#8217;re proud of the work that we’ve done for our clients and excited for the work that’s ahead of us this year. We’re busy doing what we love, with a fantastic team and a supportive network. Thanks for following along with us on our first year. With so many amazing companies in Waterloo, we know that we can keep doing what we love and having a good time while we’re at it.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Just Plain Awesome: can content be complete without being complicated?</title>
		<link>https://sparkcontent.ca/2015/10/13/just-plain-awesome-can-content-be-complete-without-being-complicated/</link>
		
		<dc:creator><![CDATA[KMoProAVD]]></dc:creator>
		<pubDate>Tue, 13 Oct 2015 13:20:44 +0000</pubDate>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Editing]]></category>
		<category><![CDATA[Plain Language]]></category>
		<category><![CDATA[Writing]]></category>
		<category><![CDATA[Karen]]></category>
		<guid isPermaLink="false">http://sparkcontent.ca/?p=330</guid>

					<description><![CDATA[Ever read the policy documents for your car insurance? How about the Terms and Conditions when you install new software? Financial statements? Even though we should read them, we probably don’t. We clip the car insurance slips and put them .....]]></description>
										<content:encoded><![CDATA[<p>Ever read the policy documents for your car insurance? How about the Terms and Conditions when you install new software? Financial statements? Even though we should read them, we probably don’t. We clip the car insurance slips and put them in the car, click “I agree” on the Terms and Conditions page, and file the paperwork. What is it about this type of content that makes us our eyes glaze over?</p>
<p>The content gets a bad rap – it has a reputation for being dense and confusing, with its complicated and detailed language. That language seems necessary – insurance paperwork, for example, should be specific about what is covered. But, believe it or not, even this content can be complete without being complicated.</p>
<p>Today is International Plain Language Day. For almost 30 years, the plain language movement has championed clear communication using clear language. The goal is to get your message across the first time that it is read. It doesn’t mean that you need to “dumb down” your content, but that you tailor your content to suit your audience.</p>
<p>Plain language has some obvious benefits. If users understand your content the first time that they read it, it saves them time, reduces their frustration, and builds their trust. You can avoid misunderstandings, errors, and, even costly customer support calls.</p>
<p>Where do you begin? Here are six strategies that you can use to apply plain language to your content:</p>
<ul>
<li><strong>Understand your audience:</strong> Ask some basic questions to understand who your audience is and what they know.</li>
<li><strong>Organize your content:</strong> Focus on what’s important to the audience and omit what isn’t necessary.</li>
<li><strong>Develop your content:</strong> Keep paragraphs to a single idea and use short sentences where you can.</li>
<li><strong>Consider your tone:</strong> Be aware of the implied tone in your writing. Make sure it’s what you want.</li>
<li><strong>Consistency, clarity, and conciseness:</strong> Revise your content. Look for inconsistent wording, eliminate unnecessary words, and use words familiar to your audience.</li>
<li><strong>Use the active voice:</strong> Brush up on the difference between passive and active voice. Use the active voice when you can.</li>
</ul>
<p>Converting your content to plain language can take planning, when you consider how much content you have. Everything from website content to social media posts to product collateral can benefit from plain language. You can phase it in over time, but you risk giving users a disjointed message. Or, you can try to time it with a particular event – a product launch or refresh, for example. That approach is better for the user, but puts a lot of pressure on writing resources.</p>
<p>At Spark, we’re passionate about plain language and can bring out the best in your content. With our knowledge and experience, we can take complicated consumer communications and apply these plain language principles. The end result is clear, complete content that readers can understand – without the extra complications.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
