This document summarizes new features in VisibleThread Docs 3.0, including a complete UI overhaul, new Excel compare capability, ability to create sub-folders, and mass import/export for readability whitelisting. It also discusses VisibleThread's journey beyond proposal tools to provide wider organizational value through their communications suite, readability tools, and email services. The document provides examples and screenshots of the new UI, Excel compare functionality, and sub-folders.
2. Part 1:
VT Docs 3.0 Update
Part 2:
Our Journey beyond a Proposal Tool to wider
organisation value
▪Communications Suite,
▪VT Readability,
▪eMail server.
4. https://www.visiblethread.com/products/visiblethread-docs/
VT Docs 3.0 – Availability & General Notes
▪ VisibleThread Docs 3.0 is available now in the cloud!
▪ 8 months in the making and lots of exciting new
features. Driven by user feedback.
▪ Live in the cloud. You’ll see all capability there today.
▪ Will be available as a FREE upgrade for on-premise
customers with current subscription or maintenance
agreement in May 2018.
▪ Any questions on any of the capabilities, mail
support@visiblethread.com
12. https://www.visiblethread.com/products/visiblethread-docs/
Why did we want to create a new compare for excel?
Mostly Customer Feedback like this one:
“Can you do a compare of excel documents in visible
thread?”
“We are working a large Army bid and the
government just issued an Amendment which
includes 30 excel files that were revised. They did
not mark the changes.”
21. https://www.visiblethread.com/products/visiblethread-docs/
Sub-folders
▪ In response to customer demand
▪ Various ways of structuring:
– By contract/RFP
– By person
– By group
▪ Advantages of folders
– easier to archive off old folders into one ‘Archive’ type folder
– better results in folder level views. Slice and dice the foldders as
you need
27. • Measure & improve the quality & readability of communications.
• Support the Digital Service Standard mission.
• Easily Audit & Report on readability improvements across the
organisation.
Project Objective:
34. DIIS Findings
• Emphasis on quality content (aligned with DTA’s Web Content Accessibility Guidelines)
• Significant web page reduction from 3,000 to 1,000 today.
• Delegation of content responsibility down the line – has resulted in improved content
quality in a faster turnaround time
• Useful as an independent ‘arbitor’ especially when working with SMEs to guide them
towards improved readability of jargon or overly technical content.
• Demonstrates value of continuous improvement.
• Improvement and efficiencies across workflow process - prior to VT this work was done
manually in Word, with screen scrape of content plagued with time consuming
functionality problems
• Full corporate knowledge management - content captured in a consistent way.
• Excellent driver in demonstrating the difference well written content makes for users’
readability
41. User authors content in an MS Word document (.docx)*
Content Author User Journey - step 1:
42. User submits document via email (as an attachment) to a dedicated email
address (e.g. analyze@readability-<your-domain-name>.com )
Use of VisibleThread email address will remove
the need for any internal IT workload.
Document is processed by VisibleThread Readability Engine
Content Author User Journey - step 2:
43. On completion an email is sent to the user with the following:
- Top line stats (coloured) Long Sentences, Passive Voice, Readability, Grade Level
Content Author User Journey - step 3:
44. Annotated document as an
attachment is returned to user.
Note: If user submits a PDF or Word
Document instead of a.docx then an
excel output will be returned instead
of annotated output
Content Author User Journey - step 4:
Fix the content in MS Word & re-submit
55. How to do this consistently, accurately and
measurably?
Checklist for Plain Language
• Write for the average reader
• Organize to serve the reader’s needs
• Use active voice
• Use short sentences
• Use “you” and other pronouns
• Use short sections
• Use the simplest tense possible
• Use base verbs, not hidden verbs
• Avoid noun clusters
• Use concrete, familiar words
• Omit excess words
• Place words carefully
• Have useful headings
• Use lists
• Use tables
• Use “must” not “shall” to express requirements
56. TBS Style Guide:
• Plain Language
• Active Voice
• Avoid Jargon
• Short Sentences
• Verify Readability
• etc.
How to do this consistently, accurately and measurably?