From a collection of templates to a “practice system” interwoven with document assembly - is this a business model that would be of use to all the would-be Basha clients out there? Let us know!
Article Content
In automating a collection of documents that form a “Practice System” there is inevitable overlap between the information required between the documents constituting the practice system. Properly attacked, there are two phases to such an automation project:
DICTIONARY PHASE
Identifying all the variables and organizing them into a series of dialogs/pages and grouping the dialogs/pages into logical interviews.
TEMPLATE PHASE
Using those variables to markup and code the templates. Many document assembly tools allow you to drag-and-drop from a dictionary/component file into a document and then save that document as a template in the practice system.
WHAT IF ....
What if the first phase could be eliminated? What if someone already had a taxonomy of variables and questions that covered most, if not all the questions you needed for the practice system? Would that be valuable? Could you use that object? And what would you pay for that convenience which could save you hundreds of hours (and tens of thousands of dollars of opportunity cost developing that dictionary)?
THEN YOU COULD ....
If you had this dictionary of variables, you could then take your forms and drag-and-drop or select-and-wizard, quickly replacing all you matter-specific information and your conditional text with codes. These could be processed through an automation tool ... and voila, you would be done with the automation project.
IS THIS A BUSINESS MODEL?
We are exploring whether this is a possible business model ... Is there a market for “practice systems” as taxonomies? Let us know.