<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Writing for the print</title>
	<link>http://maadmob.net/donna/blog/2007/writing-for-print</link>
	<description>Information architecture, interaction design and much more</description>
	<pubDate>Thu, 20 Nov 2008 11:39:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Donna Maurer</title>
		<link>http://maadmob.net/donna/blog/2007/writing-for-print#comment-815</link>
		<dc:creator>Donna Maurer</dc:creator>
		<pubDate>Mon, 15 Oct 2007 23:17:19 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2007/writing-for-print#comment-815</guid>
		<description>@Toast Yum - stews and casseroles...

Oh, back on topic. That's how I've been writing my talks lately as well - as one big story that I then illustrate.
</description>
		<content:encoded><![CDATA[<p>@Toast Yum - stews and casseroles&#8230;</p>
<p>Oh, back on topic. That&#8217;s how I&#8217;ve been writing my talks lately as well - as one big story that I then illustrate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damian (TOAST) O'Neil</title>
		<link>http://maadmob.net/donna/blog/2007/writing-for-print#comment-814</link>
		<dc:creator>Damian (TOAST) O'Neil</dc:creator>
		<pubDate>Mon, 15 Oct 2007 06:18:22 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2007/writing-for-print#comment-814</guid>
		<description>Hey Donna,

Thanks for the advice!  Along with a few other folk I know, I've started to use mind-maps to structure the things I write.  The dis-jointedness of it doesn't seem to matter, as I'm writing specifications, scoping documents and manuals, and people just read the bits they want.  (Or maybe it does... I will reflect at a later time).

*HOWEVER*, I have ambitions to do more creative writing, and I'm glad I read your post!

I write a few speeches and presentaions and I use the technique of topics/headings/subheadings, but I always make sure at some stage to "flatten" my structure, and then write the actual the actual "dialogue" in as a big block.  I may keep the original structure as a set of notes for myself, but in order to deliver a "speech" or a presentaion, it needs to be one continual.... "thing".

That said though, from my own experience and others I've talked to, you can spend 80% of your time working on the "structure" of a speech, the actual words tend to be pretty easy to write. I was even taught to pause for 20 seconds and write three bullet points when asked to jump up and do 60 seconds of impromptu.

Anyway, thanks again!  I think you've saved me from a pitfall!  Look in your local Dymocks for my global almanac of stews and casseroles (in the year 2011 or so).
</description>
		<content:encoded><![CDATA[<p>Hey Donna,</p>
<p>Thanks for the advice!  Along with a few other folk I know, I&#8217;ve started to use mind-maps to structure the things I write.  The dis-jointedness of it doesn&#8217;t seem to matter, as I&#8217;m writing specifications, scoping documents and manuals, and people just read the bits they want.  (Or maybe it does&#8230; I will reflect at a later time).</p>
<p>*HOWEVER*, I have ambitions to do more creative writing, and I&#8217;m glad I read your post!</p>
<p>I write a few speeches and presentaions and I use the technique of topics/headings/subheadings, but I always make sure at some stage to &#8220;flatten&#8221; my structure, and then write the actual the actual &#8220;dialogue&#8221; in as a big block.  I may keep the original structure as a set of notes for myself, but in order to deliver a &#8220;speech&#8221; or a presentaion, it needs to be one continual&#8230;. &#8220;thing&#8221;.</p>
<p>That said though, from my own experience and others I&#8217;ve talked to, you can spend 80% of your time working on the &#8220;structure&#8221; of a speech, the actual words tend to be pretty easy to write. I was even taught to pause for 20 seconds and write three bullet points when asked to jump up and do 60 seconds of impromptu.</p>
<p>Anyway, thanks again!  I think you&#8217;ve saved me from a pitfall!  Look in your local Dymocks for my global almanac of stews and casseroles (in the year 2011 or so).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donna Maurer</title>
		<link>http://maadmob.net/donna/blog/2007/writing-for-print#comment-813</link>
		<dc:creator>Donna Maurer</dc:creator>
		<pubDate>Sat, 13 Oct 2007 22:36:55 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2007/writing-for-print#comment-813</guid>
		<description>Gordon - my headings looked like they flowed, but when I filled them in, they were more like disconnected points than a building story.

Peter &#038; Gene. My experience is similar to yours. An outline is necessary to get a book contract, but it's not the best way to write it. I managed to write some chapters one by one as I have a chunk of procedural material (do this, then this). But apart from that, I didn't know what was in the book until it had written itself. But that's how I work - I don't know what I think until I've said it or written it down.
</description>
		<content:encoded><![CDATA[<p>Gordon - my headings looked like they flowed, but when I filled them in, they were more like disconnected points than a building story.</p>
<p>Peter &#038; Gene. My experience is similar to yours. An outline is necessary to get a book contract, but it&#8217;s not the best way to write it. I managed to write some chapters one by one as I have a chunk of procedural material (do this, then this). But apart from that, I didn&#8217;t know what was in the book until it had written itself. But that&#8217;s how I work - I don&#8217;t know what I think until I&#8217;ve said it or written it down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gene</title>
		<link>http://maadmob.net/donna/blog/2007/writing-for-print#comment-812</link>
		<dc:creator>Gene</dc:creator>
		<pubDate>Sat, 13 Oct 2007 17:45:55 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2007/writing-for-print#comment-812</guid>
		<description>That's a great story. I'll have to try that.

I've made the most progress when I've thrown out my outline.  After a couple of rocky chapters I realized that I wrote the outline to get a book contract, but the outline itself wasn't a great book.

The other thing I discovered was that I had to write the whole book, more or less, before I knew how it would turn out.  Turning things in chapter by chapter has been basically impossible.
</description>
		<content:encoded><![CDATA[<p>That&#8217;s a great story. I&#8217;ll have to try that.</p>
<p>I&#8217;ve made the most progress when I&#8217;ve thrown out my outline.  After a couple of rocky chapters I realized that I wrote the outline to get a book contract, but the outline itself wasn&#8217;t a great book.</p>
<p>The other thing I discovered was that I had to write the whole book, more or less, before I knew how it would turn out.  Turning things in chapter by chapter has been basically impossible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://maadmob.net/donna/blog/2007/writing-for-print#comment-811</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sat, 13 Oct 2007 11:09:28 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2007/writing-for-print#comment-811</guid>
		<description>I had the same happen to me. Over the years, I've started to think that the best way to write is not to make an outline first, but to teach first. Once you've taught a subject, you know how you want to explain it. Then have an approach to the structure of the book in your head, and then just write proze (and clean it up). Anyway, that's the theory, I'll try it with my next book :)
</description>
		<content:encoded><![CDATA[<p>I had the same happen to me. Over the years, I&#8217;ve started to think that the best way to write is not to make an outline first, but to teach first. Once you&#8217;ve taught a subject, you know how you want to explain it. Then have an approach to the structure of the book in your head, and then just write proze (and clean it up). Anyway, that&#8217;s the theory, I&#8217;ll try it with my next book <img src='http://maadmob.net/donna/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://maadmob.net/donna/blog/2007/writing-for-print#comment-810</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Fri, 12 Oct 2007 21:51:04 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2007/writing-for-print#comment-810</guid>
		<description>As a technical writer with IA leanings I can sympathise. One of the hardest balances I have with my work is leverage IA practises without overdoing them.

Both professions can teach each other something though, and it's odd to see you do the exact opposite of what I do. When planning content, I tend to start with an outline which is transferred into a set of headings which themselves should flow. Then the content is plugged in but written to always be relevant to it's position.

Hard, ain't it!

Good luck with the rest of the book, it'll be on my shopping list, that's for sure.
</description>
		<content:encoded><![CDATA[<p>As a technical writer with IA leanings I can sympathise. One of the hardest balances I have with my work is leverage IA practises without overdoing them.</p>
<p>Both professions can teach each other something though, and it&#8217;s odd to see you do the exact opposite of what I do. When planning content, I tend to start with an outline which is transferred into a set of headings which themselves should flow. Then the content is plugged in but written to always be relevant to it&#8217;s position.</p>
<p>Hard, ain&#8217;t it!</p>
<p>Good luck with the rest of the book, it&#8217;ll be on my shopping list, that&#8217;s for sure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
