Video: 2 minute intro; Tutorial: Worked examples; Help: Contents

Nov 5, 2009

From maps to text

Sometimes you just want the text, and nothing but the text. You've planned a report visually in bCisive Online, but now it's time to write the report in your word-processor of choice.

For example, automatically turn this

Overview of the proposed text output feature

into something like this:
Proposed feature: Text output

1. What is it for?
1.1. Example: Writing reports
1.2. Example: Writing executive summaries
1.3. Example: Extracting lists of tasks

2. What is a good starting feature set?
This what-you-see-is-what-you-get approach allows the user (or team!) to fully explore ideas by creating a really large map, but when producing the text output to be selective, and break the worthwhile parts of the map into smaller, more digestible chunks. In this example I have hidden the details of the starting feature set, which we can now reveal:

Suggestions for the initial feature set

and generate the text for these too:
2. What is a good starting feature set?
2.1. Idea: Similar to the PowerPoint output feature: Take "snapshots" of branches
2.2. Idea: Respect hide-show, so that What-You-See-Is-What-You-Get
2.2.1. Example: Only show the top two or three levels to get the draft for an exec. summary.
2.3. Idea: Filter option to get a flat list of all the boxes of a particular type
2.3.1. Example: Extract all the Tasks (probably a good default) into a list
2.4. Idea: Settings to allow or disallow automatic numbering, indentation, color, etc. (similar to bCisive desktop)
From there the idea would be to polish up the text in your word-processor (or email software, etc.) and either maintain outline form; edit it into a traditional text of headings, paragraphs, and sentences; or, perhaps most likely, create a mix of both.

No comments: