<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel xmlns:blog="http://www.dotnetnuke.com/blog/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <title>Mark Scott</title>
    <description>___________________________________________________________________________________________________</description>
    <link>http://www.framegroup.com.au/Blog/tabid/109/BlogId/4/Default.aspx</link>
    <language>en-AU</language>
    <webMaster>mark.scott@framegroup.com.au</webMaster>
    <pubDate>Thu, 09 Sep 2010 21:57:43 GMT</pubDate>
    <lastBuildDate>Thu, 09 Sep 2010 21:57:43 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 4.0.0.0</generator>
    <item>
      <title>Seven tips to improve the quality of your business writing</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/59/Seven-tips-to-improve-the-quality-of-your-business-writing.aspx</link>
      <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;span style="font-size: 10pt"&gt;&lt;img height="80" alt="" width="60" align="left" vspace="3" src="/Portals/0/MarkScott.jpg" /&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;If you spend a lot of time writing, ensure your effort is not wasted. How? I’m glad you asked.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;I’ve been participating in &lt;a target="_blank" href="http://www.linkedin.com/"&gt;LinkedIn&lt;/a&gt; discussions about the quality of writing ... well, the lack of it. And I’ve read pieces in the press about the falling standards of English, like &lt;/span&gt;&lt;span style="font-size: 10pt"&gt;&lt;a target="_blank" href="http://www.smh.com.au/technology/technology-news/internet-spells-death-of-english-20100104-lq7s.html"&gt;this article&lt;/a&gt; in the &lt;i&gt;&lt;a target="_blank" href="http://www.smh.com.au/"&gt;Sydney Morning Herald&lt;/a&gt;&lt;/i&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;This got me thinking about the amount of formal business documentation that gets released without being properly proofread, edited and reviewed.&lt;/span&gt;&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/59/Seven-tips-to-improve-the-quality-of-your-business-writing.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/59/Seven-tips-to-improve-the-quality-of-your-business-writing.aspx</guid>
      <pubDate>Wed, 01 Sep 2010 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=59</trackback:ping>
    </item>
    <item>
      <title>Just how long is that piece of string?</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/55/Just-how-long-is-that-piece-of-string.aspx</link>
      <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;img height="80" width="60" align="left" vspace="3" alt="" src="/Portals/0/MarkScott.jpg" /&gt;‘But it’s 118 pages long!’ exclaimed the project manager. ‘We can’t expect a service provider to read this when they turn up to do work for us.’&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;Picture this: I’m at a meeting with a client (a big Aussie company), presenting the draft of a document I’ve just completed for them. We (that’s me and the team I wrote the document for) are now socialising the document within the organisation. Considering what was presented, I was somewhat taken aback (to put it mildly) that the comment about the document’s length was the first piece of feedback we received.&lt;/span&gt;&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/55/Just-how-long-is-that-piece-of-string.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/55/Just-how-long-is-that-piece-of-string.aspx</guid>
      <pubDate>Wed, 21 Jul 2010 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=55</trackback:ping>
    </item>
    <item>
      <title>Love me, tender, part 4: it’s my party and I’ll cry if I want to</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/51/Love-me-tender-part-4-it-s-my-party-and-I-ll-cry-if-I-want-to.aspx</link>
      <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;img height="80" alt="" width="60" align="left" vspace="3" src="/Portals/0/MarkScott.jpg" /&gt;In this last part of my &lt;a href="http://www.framegroup.com.au/Blog/tabid/109/BlogID/4/Default.aspx"&gt;&lt;i&gt;Love me, tender &lt;/i&gt;series&lt;/a&gt;,&lt;i&gt; &lt;/i&gt; I attack … I mean, I cast a critical eye over the response requirements for procurement documents. By ‘response requirements’ I mean the content you expect from a service provider to demonstrate they’re right for the job, and how you want that content to be presented.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;Read my three final tips for procument document writers.&lt;/span&gt;&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/51/Love-me-tender-part-4-it-s-my-party-and-I-ll-cry-if-I-want-to.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/51/Love-me-tender-part-4-it-s-my-party-and-I-ll-cry-if-I-want-to.aspx</guid>
      <pubDate>Wed, 09 Jun 2010 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=51</trackback:ping>
    </item>
    <item>
      <title>Love me, tender, part 3: please, please me</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/47/Love-me-tender-part-3-please-please-me.aspx</link>
      <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;img height="80" alt="" width="60" align="left" vspace="3" src="/Portals/0/MarkScott.jpg" /&gt;Do you get lots of requests for clarification to your RFPs and other procurement documents? Do you receive responses with varying content and levels of detail that make comparison difficult? These are measures of how clear your procurement documents are.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;The question is: how can you make them clearer?&lt;/span&gt;&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/47/Love-me-tender-part-3-please-please-me.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/47/Love-me-tender-part-3-please-please-me.aspx</guid>
      <pubDate>Wed, 07 Apr 2010 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=47</trackback:ping>
    </item>
    <item>
      <title>Love me, tender, part 2: listen, do you want to know a secret?</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/43/Love-me-tender-part-2-listen-do-you-want-to-know-a-secret.aspx</link>
      <description>&lt;p&gt;&lt;span style="font-size: 10pt;"&gt;&lt;img width="60" vspace="3" height="80" align="left" src="/Portals/0/MarkScott.jpg" alt="" /&gt;It’s essential that you consider how service providers will interpret and use your procurement documents. With timeframes to meet and the effort required to get tenders out the door, the less confusion for service providers, the better. After all, service providers are the primary audience of your document.&lt;/span&gt;&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/43/Love-me-tender-part-2-listen-do-you-want-to-know-a-secret.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/43/Love-me-tender-part-2-listen-do-you-want-to-know-a-secret.aspx</guid>
      <pubDate>Wed, 10 Mar 2010 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=43</trackback:ping>
    </item>
    <item>
      <title>Love me, tender, part 1: an expression of vested interest</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/39/Love-me-tender-part-1-an-expression-of-vested-interest.aspx</link>
      <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;font size="2"&gt;&lt;img height="80" width="60" align="left" vspace="3" alt="" src="/Portals/0/MarkScott.jpg" /&gt;Given the cost of developing procurement documents, organisations need to take care to achieve the best possible outcome. Just look at what’s at stake: the commitment to a solution or service, with its associated—and potentially large—financial transaction, contract period and changes to business operations.&lt;/font&gt;&lt;/span&gt;&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/39/Love-me-tender-part-1-an-expression-of-vested-interest.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/39/Love-me-tender-part-1-an-expression-of-vested-interest.aspx</guid>
      <pubDate>Wed, 10 Feb 2010 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=39</trackback:ping>
    </item>
    <item>
      <title>Lost in transcription</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/13/Lost-in-transcription.aspx</link>
      <description>&lt;div&gt;&lt;img width="60" vspace="3" hspace="3" height="80" align="left" alt="" src="/Portals/0/MarkScott.jpg" /&gt;The way you write is a reflection of the way you think. That means your documentation affects people’s perception of your ability. The cleverness of your work can be diluted and even lost if it’s not matched by top-quality documentation.&lt;/div&gt;
&lt;div&gt; &lt;/div&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/13/Lost-in-transcription.aspx#Comments</comments>
      <slash:comments>2</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/13/Lost-in-transcription.aspx</guid>
      <pubDate>Wed, 18 Nov 2009 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=13</trackback:ping>
    </item>
    <item>
      <title>Three tips for better flowcharts</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/12/Three-tips-for-better-flowcharts.aspx</link>
      <description>&lt;p&gt;&lt;img width="60" vspace="3" hspace="3" height="80" align="left" src="/Portals/0/MarkScott.jpg" alt="" /&gt;I hate flowcharts!  Harsh, yes, so allow me to explain …&lt;/p&gt;
&lt;p&gt;As a means of mapping or modelling a process, socialising and refining it, and as a visual representation of it, flowcharts are hard to beat.  They make processes easier to define, understand and follow.  But as the final documented form of processes, flowcharts aren’t always effective.&lt;/p&gt;
&lt;p&gt;It's not flowcharts per se that are the problem—it's that, often, they’re poorly drawn.  And that's why I hate flowcharts.&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/12/Three-tips-for-better-flowcharts.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/12/Three-tips-for-better-flowcharts.aspx</guid>
      <pubDate>Wed, 07 Oct 2009 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=12</trackback:ping>
    </item>
    <item>
      <title>The benefits of MS Word templates</title>
      <link>http://www.framegroup.com.au/Blog/tabid/109/EntryId/11/The-benefits-of-MS-Word-templates.aspx</link>
      <description>&lt;p&gt;&lt;img height="80" alt="" hspace="3" width="60" align="left" vspace="3" src="/Portals/0/MarkScott.jpg" /&gt;MS Word templates … do you use them?&lt;/p&gt;
&lt;p&gt;When I say ‘template’, I don’t mean a single-paged document with a few headings that you have to try and craft a report from.  I mean a multi-paged fully-branded document based on a company-wide style sheet.  And I mean a structured document with standard headers, footers, sections, headings, and lots of instructions to explain what’s expected of the author.&lt;/p&gt;
&lt;p&gt;So, why bother with templates like that?&lt;/p&gt;</description>
      <author>mark.scott@framegroup.com.au</author>
      <comments>http://www.framegroup.com.au/Blog/tabid/109/EntryId/11/The-benefits-of-MS-Word-templates.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.framegroup.com.au/Blog/tabid/109/EntryId/11/The-benefits-of-MS-Word-templates.aspx</guid>
      <pubDate>Tue, 07 Jul 2009 14:00:00 GMT</pubDate>
      <trackback:ping>http://www.framegroup.com.auDesktopModules/BlogTrackback.aspx?id=11</trackback:ping>
    </item>
  </channel>
</rss>