Using Natara Bonsai with WorkFlowy

Natara Bonsai has long been my favourite outliner, but in the last couple of years it has been gradually displaced in my daily use by WorkFlowy, mainly because WorkFlowy syncs automatically and seamlessly across all my devices using different platforms, which is very useful for capturing notes and todos and having them always available.

Nevertheless, there are situations where Natara Bonsai is still my go-to choice. For example, when I need to organise, analyse, sort and resort large lists, or when I need to hierarchically structure some complex information, where it helps that different hierarchical levels can be displayed in different colour, to guide the eye.

Fortunately it is very easy to get information from Natara Bonsai back into WorkFlowy. All you need to do is install the OPML export template from the CarbonFin website (instructions available there), then export the Bonsai outline as a .opml file, open the .opml file using your favourite text editor (for this task I like to use Notepad++), and simply copy and paste the contents of the .opml file directly into a WorkFlowy bullet point. WorkFlowy will not only preserve the outline hierarchy but it will also display any Bonsai outline item notes as inline WorkFlowy notes.

Here is a Bonsai outline (the final bullet point has a note, displayed in the pane on the right):

Natara_Bonsai_12_03_2016

And here it is after having been pasted into WorkFlowy (note the inline note under the last bullet point):

WorkFlowy_screenshot.png

Addendum:

Frank Degenaar points out in the comments section that it is possible to add colour to a WorkFlowy outline as well, using the “Painter for WorkFlowy” Chrome add-on and some stylesheets using the “Stylish” add-on. That is definitely true and I do make use of those tools in my WorkFlowy all the time. It would only take me a minute or two to reconstruct the colour scheme of the above Bonsai outline in WorkFlowy, and the two would look fairly similar (especially if I change the dark WorkFlowy theme to a light one).

However, the colouring-in capability of Natara Bonsai works quite differently from that of WorkFlowy and serves a different purpose. You can set up Bonsai so that it automatically colours in your outline items according to the outline level position they occupy. This means that if you promote or demote an outline item, its colour will change accordingly and automatically.

While it is possible to retrospectively colour in a WorkFlowy outline by adding a colour tag to each item individually and manually (which would be time-consuming in the case of very large and multi-level outlines), these colours will not change when you demote or promote these items, as their colour tags will travel with them.

The  key point here is that when using Bonsai, the colour scheme has already been set up as default (using the procedure I described earlier), so I don’t have to pay any attention to the colouring-in, it just works automatically as I type away and keep promoting and demoting items. In contrast, with WorkFlowy the colouring-in needs to be done manually, individually for each item, and retrospectively, after the item has been added, and it does not change, if I move the outline items, thus breaking the logic of the “colour by hierarchy level” scheme.

This difference becomes significant when you want to work on large and complex lists and you want to pay attention to the text, rather than be disrupted by the mechanics of colouring-in. Bonsai just allows you to work faster, without having to make decisions about and fiddle with every single item, as you would have to in WorkFlowy.

By the way, as I have already explained in that earlier post, it is possible to use other criteria for the automatic colouring in Bonsai, such as category, priority or due date.

Natara Bonsai downloadable from the Internet Archive

I still get visitors coming to this site looking for the outliner Natara Bonsai almost daily, as I mentioned it occasionally that it was one of my alltime favourite pieces of software. Unfortunately the Natara Bonsai download page went down sometime in 2014, never to come back again. There is now only a placeholder page for the main Natara site that points to the Natara blog (the last post on which dates 6 June 2013).

A few months after the Bonsai site has disappeared, I stumbled upon some kind of a mirror site at http://64.226.29.51/Bonsai/Download.cfm where it was still possible to download the software from. I was very happy to share that link, and I got a few emails from Bonsai fans thanking me for it. Apparently Bryan Nystrom, the owner of Natara Software, Inc., was kind enough to sell them a licence.

Alas, a few months ago this mirror site has also gone down. It seemed that Natara Bonsai was well and truly gone. I was kicking myself for not having taken some screenshots of that site at least, just as a keepsake (yes, that is how much I love this software). Then one day it occurred to me: what if there are some archival pages of the Natara site on the Internet Archive? And lo and behold, there indeed are a number of such pages. And not only that: the Bonsai files can still be downloaded from there! Here is one such link for instance: http://web.archive.org/web/20110519183308/http://www.natara.com/bonsai/Download.cfm

I cannot vouch for the safety of these files, so download and run them at your own risk. But chances are they might just be the original Natara Bonsai files. So fellow Bonsai fans, rejoice!

Natara_Bonsai_Internet_Archive_2011_05_19

Alternative Natara Bonsai download site

My blog stats tell me that there is a steady stream of visitors looking for Natara Bonsai, ever since the main download site has disappeared a few months ago. It seems that there is still at least one site where Bonsai 5 Desktop Edition can be downloaded from (and there may very well be some others out there). I don’t know whether this site is legitimate, so download anything at your own risk, and make sure you scan the file for viruses. However, I know of at least one reader who has done so, and he sounded happy. Here is the link: http://64.226.29.51/Bonsai/Download.cfm. It seems to be some sort of a mirror of the original site, as it looks identical. If you do not have a license, you could try to contact the administrator of the Natara blog to find out if it is still possible to purchase one.

Natara Bonsai

Natara Bonsai is one of my old time favourites. While there are some other capable outliners out there, when I need to analyse textual data in long and complex lists, none are as easy and fast to use as Bonsai. The last version I have is v. 5.0.3 Build 3233. I run it on a Win 7, 64-bit machine, and it works perfectly.

Taking reading notes with Freeplane

For some time now I’ve been using Freeplane as my reading-note capturing application. I would be reading a book at my desk, in front of my computer monitor(s), and use Dragon NaturallySpeaking to dictate my notes and quotes into DragonPad first, and then paste them into Freeplane. In the case of electronic materials, mainly journal articles in PDFs, I would convert the PDF into a Word file with ABBYY FineReader (so that I preserve word-wrapping and formatting while copying), and then would paste the quotes into Freeplane.

What are the advantages of this method? Firstly, it allows me to reverse-outline the book’s argument by organising the quotes and notes into a hierarchical mind map. Such a reverse outline helps with reconstructing and understanding the main train of thought of the reading, as the hierarchy records logical relationships between ideas. Here the mind map format has an advantage over a traditional vertical outline, as the individual nodes are easier to see and comprehend when distributed across a wide monitor in landscape form.

Secondly, each node can have a title and a note, and the latter can be seen inline (as opposed to being separated into another pane, as in most dual-pane outliners). Also, Freeplane can preserve rich text formatting (unlike let’s say Natara Bonsai). You can use icons and different styles to mark important notes. It is easy to restructure the outline by dragging and dropping nodes and branches around.

Thirdly, it is easy to convert a Freeplane mind map (which uses Freemind’s .mm file format) to other file formats. I use iThoughtsHD on iPad as my Swiss-Army Knife converter of mind map formats. I usually convert it into OPML, in order to import it into Bonsai, if further organising and analysis is needed, or simply to convert it into RTF, so that it can be imported into my main database, ConnectedText, which is the final destination of all my notes. I also link to all the different formats of a file (.mm, .opml, .otl, .rtf) from the final CT document, so I can easily find them later.

But Freeplane is useful not only for capturing and organising my reading notes into a hierarchical outline. It also comes in handy when it’s time to write up the notes for a chapter or article. I start a new Freeplane file as my outline for the new piece of writing, and I can simply copy and paste selected nodes and entire branches of quotes and notes from other Freeplane files, thus gathering relevant information for one author from let’s say five other mind maps with notes for five books by that author. (It is useful though to have two monitors for this, to take full advantage of the landscape orientation of mind maps.) Then as I write the final piece, I use a big red X icon to mark off the nodes and branches that have already been discussed.

Freeplane reading notes

I hear people complain about Freeplane not being pretty or visual enough. To me that is an advantage. I find pretty colour schemes distracting. All I want is black font and a white background. I do like the automatic colouring-in of the lines representing the branches, as that guides the eye and helps comprehension. But otherwise I want to be the one who decides when to apply additional colour or an icon to introduce new visual information. And I only do that to highlight important nodes, so I can quickly pick them out from a complex mind map. I thank the developers for keeping the main interface simple.

By the way, don’t be confused by the screenshots on the Freeplane website. Obviously, the developers are trying to show off all the different features. However, pretty much all the colour noise can be switched off, and you can use it as a minimalist, almost black-and-white (or whatever colour-combination you like) note-taker and organiser.

 

Using colour in outlining

I was glad to see that the latest version (3.6.3b) of Noteliner now supports “unlimited colors for lists, note highlighting and sections of text.” For me colour has always been an important factor in outlining. There seem to be two main approaches.

Noteliner exemplifies the approach whereby you are given complete manual control over changing the colour of the foreground (the font) or the background (highlighting text). This approach comes in handy when you want to mark up an existing outline in different colours to emphasise particular meanings or functions. The downside is that it is a manual process, so in the case of a long outline it would be rather fiddly to be changing every item to a different colour.

This is where the alternative approach excels: outliners that provide an automatic colouring-in option using some kind of a template. Natara Bonsai 5 (Desktop Edition) — my favourite single/dual/triple etc.-pane outliner — does this very well. If you choose Outline > Text Color from the main menu, you are presented with four options.

Natara_Bonsai_edit_colorsYou can colour in your outline automatically according to each outline item’s category, priority or due date, assuming that you have added these values to the outline items.

My favourite feature is the fourth option, “By Level,”  which means that each outline item will be coloured in according to its place within the hierarchy (available up to 16 levels). You can even select a custom colour for the completed items, in case you opt to have a check box in the outline.

Natara_Bonsai_color_by_attributeBelow is an example of such a coloured-in outline. I like this feature because it makes it so much easier to analyse a long, complex outline and comprehend the relationships between concepts at different levels of the hierarchy.

Natara BonsaiAlso, under View > New Outline Defaults you can set up a colour scheme for any new outline, whether created from scratch or imported or pasted in from elsewhere. The colouring-in options are saved thereafter for each new outline.

The downside of this approach is that (at least in Bonsai) there isn’t a way to do ad hoc highlighting or colouring-in of font (as there is in Noteliner). It would be nice if one could still mark up an automatically coloured-in outline with additional highlighting.

Other outliners I’m aware of that can do some colouring-in are StoryView/Outline 4D, Inspiration, BrainStorm, and UV Outliner.

Update (26/07/2013):

There is also Redhaven Outline, which has an interesting implementation of colours (see their Youtube video on that).

Academic writing process and associated tools

The main stages of my academic writing process:

  1. Note-taking (empirical data collection or taking reading notes);
  2. Analysis and evaluation, resulting in
    • an abstracted list of observations;
    • a selection of evidence (quotes and notes);
  3. Organising these findings by: [2 and 3 can be done concurrently]
    • Ordering the list into a hierarchical outline;
    • Attaching selected evidence to list items;
  4. Developing a separate outline for a draft (journal article or thesis or book chapter):
    • creating a hierarchical list of items (titles);
    • attaching a selection of evidence (quotes and notes) to the items as inline notes;
  5. Writing the draft;
  6. Adding a reverse outline (headings and subheadings) to the draft [5 and 6 are a more or less simultaneous, recursive process] .

academic writing process

Tools needed:

  1. Note-taking (empirical data collection or taking reading notes);
    1. TOOLS:
      • CT (ConnectedText) – Clipboard Catcher (or clipboard extender)
      • Nebulous Notes on iPad/iPod Touch > Dropbox > CT
      • Dragon NaturallySpeaking (on PC) > CT
      • GoodReader, PDF Expert on iPad > email > CT
  1. Analysis and evaluation, resulting in
    • an abstracted list of observations;
    • a selection of evidence (quotes and notes);
    1. TOOLS:
  1. Organising these findings by: [2 and 3 can be done concurrently]
    • Ordering the list into a hierarchical outline;
    • Attaching selected evidence to outline items;
    1. TOOLS:
      • CT outline (occasionally exported to and imported back from Natara Bonsai)
      • CT outline + linked CT topics
  1. Developing a separate outline for a draft (journal article or thesis or book chapter):
    • creating a hierarchical list of items (titles);
    • attaching a selection of evidence (quotes and notes) to the items as inline notes;
    1. TOOLS:
      • CT Project Outline with links to topics
  1. Writing the draft;
    1. TOOLS:
      • Outline 4D
      • Freeplane
  1. Adding a reverse outline (headings and subheadings) to the draft.
    1. TOOLS:

Update (24/01/2013)

The above chart could have been more representative by having an arrow between ConnectedText in Step 4 and Freeplane in Step 5, as the CT project outline would be exported as a .mm file and imported into Freeplane. This is an important relationship as the links to the selected CT topics will be preserved and remain clickable, thus turning CT+Freeplane into a virtual dual-pane outliner/notes organiser.

Also, Steps 5 and 6 should have been alongside each other or at least there should have been arrows pointing back from 6 to 5, as the reverse outlining process is part of the drafting process. After writing 3 or 4 paragraphs I immediately add headings and sub-headings and slot them into Outline 4D’s single-pane hierarchical outline.

Update 2 (24/01/2013)

Here is an amended chart, taking into consideration the above corrections:

academic writing process 2Update 3 (24/01/2013)

Upon further reflection this is still not an entirely accurate picture of the entire process and set-up. An additional element emerges in Stages 5 and 6: the management of writing fragments that have to be removed from the draft in Outline 4D during interim editing and need to be kept apart. I may reuse some of these later, if and when the need arises.

Initially I just used a text document in NoteTab for this. But as the number of fragments grew, I needed a more sophisticated solution with the ability to split text into paragraphs and rearrange them in a hierarchical outline. For now I’ve been using Scrivener for Windows for this, which works well as a two-pane organiser of notes and also has the handy “split selection with title” command for breaking up a text into segments. However, I find Scrivener a bit of an overkill (and too slow on my Windows 7 system) for this. I’d prefer to use a lightweight, small footprint two-pane outliner that allows for the easy rearrangement of fragments.

Developing a final outline

The problem with developing a final outline for a PhD dissertation chapter is that it is difficult to know when the outline is really final. It will be final of course when you are confident enough that it is of the requisite quality. The difficulty is how to identify the boundary between the conceptual development stage and the stage of writing-up for presentational purposes.

For academic writing it is the former that is the main headache, i.e. coming up with the content, rather than putting it into its final shape. It happens all too often that you think you are in the second stage, only to discover that you have more conceptual development and clarification to do, and you are thrown back into stage 1.

For now I can’t seem to find a better answer than to push on with aiming to reach a final outline, even if it turns out to be an interim stage of conceptual development. Then I just start developing a new “final” outline, hoping that it will really be the final one. As part of this process I am constantly switching between software tools, in search for specific features more suitable for the particular tasks in the subsequent stages of development.

This reflexive and recursive process of dealing with multiple outlines in multiple software tools eventually reveals an arrangement of outlines in an arrangement of software tools, and a shape-shifting process flow that adjusts itself continuously. It is like an experimentally assembled moonshine distillery for the purpose of abstraction to be achieved by routeing ideas (textual content) from one vessel to another, until they acquire sufficient clarity to be bottled and labelled and sold to a discerning public.

Here is a slightly revised graphic (following on my previous post) showing the current distillery and the process flow. Its shape has become slightly clearer to me.

writing-up process flow

On  the left we start with the notes database in ConnectedText. It is the base, the alpha and the omega. It contains the fruits of my research work. However, I now need to extract the spirit and the flavours with my distillery apparatus. Initially I extracted and organised the main conclusions in Natara Bonsai outlines. Bonsai is the fastest tool I have for organising lists into meaningful hierarchies and then drawing ‘final’ conclusions from these conclusions.

Parallel to this I have been developing a chapter outline in Outline 4D. I have also used O4D to summarise some ConnectedText meta topics which were already extractions of important findings (as opposed to the summaries of specific articles that have been analysed in Bonsai). As O4D allows for inline notes in its outlines, I have also pasted in selected quotes (from CT, which came from the original readings) to support particular outline items (my observations).

I also have a 7000-word draft in MS Word that I wrote at an earlier stage partly as an effort to break out of the circular outlining process and force myself to finish this stage (the target is a 10,000-word chapter). However, the draft writing process just turned out to be another stage of the distillery, as I have found some gaps in my conceptual structure. It felt like Word was a laboratory where I tried to assemble the parts but the trial failed and I needed to get back to the drawing board.

VUE was the drawing board, and concept mapping was the process of drawing out the issues for my conceptual apparatus and reorganise my argument. VUE was a kind of an experimental space, a sandbox. It is placed at the top of the diagram because it is an overview of everything that is going on. First I created a reverse outline of my Word draft, to get a better understanding of my argument so far. Then I also developed an outline (well, more of a concept map) for the next stage of writing.

I should mention that I also have an overall outline for the entire thesis kept in a Scrivener project, which contains some relevant material for this current literature review chapter as well. I will need to review it as I embark on constructing my “final” outline.

I have settled on a Freeplane mind map as a way of constructing my “final” outline, which would hopefully lead me through the final – presentational stage – of writing up. In the past I didn’t quite see the point of formal mind maps, as I preferred the freedom of concept maps. But now I see that a mind map – combined with Freeplane’s functionalities – is an excellent way to develop a final outline.

First, a mind map forces you to define a final hierarchical order between sections, ideas and paragraphs, which the final draft needs to have. Secondly, a Freeplane mind map is very economical with screen space, allowing you to cram a lot of information in and be able to navigate it and visualise it easily. Thirdly, it allows you to switch between a mind map and an outline view. Fourthly, it allows you to add notes to items, which can be chosen to be displayed inline, effectively operating as a single-pane outliner with inline notes (of which only a handful exist in the world).

Fifthly, it allows you to export into RTF file format in such a way that the inline notes get displayed below their items, and the items are assigned headings according to their hierarchical level. So for example in Word or LibreOffice, items can be viewed as section headings in the Navigator window, a set-up that can be used as a dual-pane outliner. Also, the headings can be used to create a table of contents.

Finally, (building on the fourth and fifth point), you could construct a complete sentence outline in Freeplane by using items as topic sentences and notes as the evidence to support the topic sentences (e.g. quotes or other details). Even a simple “copy and paste” into Word creates a bullet-pointed hierarchy, which then can be transformed into a draft (although with this export method you don’t get the headings formatting preserved – but that may be preferable in some situations).

I am planning to do the final writing in Outline 4D though (which will require importing the RTF file with the headings and notes), in recognition of the possibility that this “final” Freeplane outline may not turn out to be entirely final, and rather than create yet another reverse outline or concept map to keep track of the underlying and implicit conceptual structure, I could just use O4D’s outlining functionalities to keep track of the evolving implicit outline of the draft. This could also be done in Word, simply by modifying the headings that get displayed in the Navigator (as a dual-pane outliner set-up). However, I find O4D’s single-pane view more conducive for this simultaneous writing and real-time (reverse) outlining, as O4D has many helpful alternative visualisations of the text and the outline.

Do I worry that I get carried away with playing around with software tools instead of doing the writing? You bet. Although there is definitely a ludic aspect to this, in the end the distillation process is real and necessary. I would need to carry out the abstraction process somehow in any case. I am hoping that by constructing a sophisticated distillery I will be able to extract and construct a higher quality final product.

Could I be wrong about that? Yes, that is a distinct possibility. However, academic research is by definition an experimental process and experiments (and experimenters) can fail (and they often do), perhaps even more frequently than they succeed (which is why so many PhD students never complete their theses). All I can do is carry on and hope that my experimental process and set-up produce a satisfactory result.

Analytical process flow for reading notes in ConnectedText

Currently I’m working on my literature review. Here is my analytical process flow for importing data, analysing it, and outputting information using ConnectedText (CT) and a variety of other tools. This process flow is just a snapshot, it’s not set in stone. It keeps changing as my needs change and as I gradually develop approaches that better suit the creative process of analysis, evaluation and synthesis.

  1. Importing reading notes into CT:
    1. I read and annotate academic articles in PDF form using GoodReader (if the text can be highlighted) or PDF Expert (if the PDF is a scanned image) on an iPad.
    2. Then I email the notes (highlighted text + my comments) and the annotated file to myself.
    3. On the PC I replace the original PDF file with the annotated one, re-link my EndNote reference to it, and copy and paste the highlights and the comments from the email into a new CT topic in my “Readings” project (CT database) under the ==Quotes/Comments== heading in my CT reading notes template.
    4. With printed books (i.e. not e-books) I take notes using a pen and a paper notebook, and when I’m finished, I use Dragon NaturallySpeaking to dictate the selected quotes and my comments into DragonPad, from where I copy and paste them into the CT template as described above.
  2. Analysing and evaluating reading notes in CT:
    1. I use CTRL+H to “search and replace” (also available from Search > Replace) the headings inserted by GoodReader/PDF Expert with either ===Quote: === (for highlighted text) or ====Comments: ==== (for my own comments).
    2. I review the text and extract the essence of the quoted text and comments and add it into the headings, such as ===Quote: cognitive functions are socially acquired===, followed by ====Comment: I agree with this====.
    3. I use yellow colour to highlight particularly important quotes and comments.
  3. Organising conclusions:
    1. If the CT topic is short, I can develop and record my conclusions immediately under the heading =Evaluation=. I summarise my main point in a final couple of sentences under =Verdict=, including them in the attribute [[Verdict:=My concluding sentences go here.]], so that they show up in the Infobox at the top of my CT topic.
    2. If the CT topic is long (i.e. it contains a lot of imported quotes and comments), then I need to use additional tools to organise the annotated headings.
      1. I remove the [[$NOTOC:]] markup from my template, so that the Table of Contents (TOC) becomes visible within the topic.
      2. I highlight the contents of the TOC, right-click, copy, and paste it into a blank Natara Bonsai document. In Bonsai I already have the new document template set up, so that different hierarchical levels appear in different colours, to aid the sorting of information.
      3. Using Bonsai’s outlining functionality, I reorganise the imported contents of the CT TOC into a meaningful hierarchy.
  4. Developing an outline for the draft chapter:
    1. The whole purpose of evaluating reading notes is to come up with my own interpretation, supported with evidence. The next (and parallel) stage is to develop an overall outline for the draft thesis chapter. Depending on the complexity of the material, it may require several tools still:
      1. I keep CT open to be able to view given reading note.
      2. I consolidate material (my main points supported by key quotes) in a final Outline 4D outline (which is a single-pane outliner that can have inline notes, in contrast to Bonsai.)
      3. During this whole process I use an overall VUE concept map to work out relationships between concepts and to develop an argument.
      4. I record the very final overall outline in the form of a Freeplane mind map.
  5. Writing up:
    1. to manage the final writing-up process, I use MLO to record to-dos as they develop.
    2. I do the final writing-up in an Outline 4D document. The advantage of using O4D for this is that it obviates the need for another application to do reverse outlining as the text grows, because it is easy to alter headings for multiple hierarchical levels and toggle them on and off, when you only want to see the text. I find this better than dual-pane alternatives such as Word with Navigation Pane or Scrivener.
    3. To add references, I simply type the reference such as (Smith 2008: 35), so as not to be distracted and disrupted by having to switch to EndNote every time (and it is not compatible with O4D anyway).
    4. I export O4D text to Word.
    5. I replace manual references with EndNote references, to build bibliography.

Here is a graphic just showing the latter stages of my writing-up process flow. I embed these types of process flow graphics in the home page (dashboard) of my reading notes wiki, so that they remind me every time I get stuck. Chances are that in a few days it will be replaced with a modified process flow, as I keep tinkering with it.

writing-up process flow

Academic writer’s block cure

In my previous post I discussed how I turned to writing as a way to put a stop to my obsessive-compulsive outlining behaviour. Outlining is certainly an important part of preparing for writing, but not if outlines keep on begetting further outlines and there is no end in sight to the proliferation of outlines. The white space of the empty Word document acted as a laboratory or workshop where I could cobble together the various conceptual threads, while still keeping a reverse outline to monitor the emerging shape of the argument. This strategy worked fairly well for a while, and I ended up with about 3000 words that I’m reasonably happy with.

Then I got stuck. Now, I’m sure lots of things have been written about the writer’s block, and I don’t have time to read any of it. So apologies if I’m stating the obvious. But I’ve been finding that there are usually two reasons why I get stuck: either I haven’t worked out the content of what I’m going to say (the conceptual point) or I haven’t worked out in sufficient detail the practical steps (workflow) that I need to take. The two reasons are closely interrelated because usually I need to work out the practical steps to be able to develop the conceptual points.

At this stage of the game however I couldn’t fathom developing yet another linear outline in a traditional one-pane or two-pane outliner to work out the next steps. One reason why I’m finding linear outlines less helpful towards the end of my project is that this stage requires synthesis, which is about putting things back together, rather than laying them out in a line (out-line). Synthesis requires matrix-type tools, as there are at least two “dimensions” that need to be brought together (if we consider a linear outliner a one-dimensional tool).

There are a number of ways to create such a matrix effect. One could just use a table (Word) or a spreadsheet (Excel) or columns in a one- (Bonsai) or two-pane (myInfo) outliner. I particularly like to use TreeSheets for this type of matrix-outlining. However, this time I reached for my favourite concept mapper, VUE, again, as it was a lopsided matrix that I had in mind, where one axis had a lot more content than the other and I needed the ability to visualise the shape of the whole thing, no matter what size it grew to.

I am working on a literature review chapter and I needed to evaluate the work of a major author. I had to review my notes on seven of his works (kept in ConnectedText), extract the main points and organise them into separate outlines in Bonsai, and finally consolidate them into a single outline. It was this last step that I used VUE for. I ended up with a concept map that looks like this:

VUE_concept_map2

The matrix is constituted by the analytical lens on the right-hand side (grey nodes), which was applied to evaluating the rest of the nodes. When I started the mapping and review process, I thought I only had three sub-topics to write about. Conceptual development occurred as part of this mapping process, and I ended up discovering that I had three more important things to say. Finally at the bottom I drew some conclusions from the material.

The advantage of doing this in VUE (as opposed to a traditional one- or two-pane outliner) was that I didn’t need to worry too much about an overall hierarchy initially. Any node can be linked to any other node, and while there is a certain hierarchy here (the overall argument flows from top to bottom, and section arguments flow from left to right and down), working in a concept map feels more fluid and free than in a linear outline. It is just a matter of different visualisation, as all of this could have been done in an adequately equipped one-pane outliner as well.

So what are the next steps? Now that I know what I want to say in this part of my chapter, I can write an introduction that will state what is going to be said, with a thesis sentence that combines the topic sentences of the six sections and points towards the contributions that will be summarised in the conclusions. My plan is to keep this concept map open in my second monitor and use it as a guide while I dictate my text into Word with Dragon.