<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DEQESXo4eSp7ImA9WxNUGUs.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233</id><updated>2009-11-11T14:05:08.431-05:00</updated><title>The Exari Blog</title><subtitle type="html">Thinking out loud about contracts</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.exari.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://blog.exari.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>122</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/TheEngineRoom" type="application/atom+xml" /><feedburner:emailServiceId>TheEngineRoom</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;D0AGQX86fCp7ImA9WxNUFE4.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-7867870956797179770</id><published>2009-11-05T10:42:00.003-05:00</published><updated>2009-11-05T10:42:00.114-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-05T10:42:00.114-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="london" /><category scheme="http://www.blogger.com/atom/ns#" term="insurance" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><category scheme="http://www.blogger.com/atom/ns#" term="assembly" /><title>Breaking the "Groundhog Day" Curse</title><content type="html">In this month’s &lt;a href="http://www.globalbrokermagazine.com/nov2009-lloyds.html"&gt;Global Broker and Underwriter Magazine,&lt;/a&gt; Lloyd’s CEO Richard Ward, talks about the market’s need to “get it’s act together” to provide better service to its clients, or risk them going elsewhere. He emphasises the need for the market to embrace the Lloyd’s Exchange initiative and says that, “To some respects the market is like a Groundhog Day as nothing has materially changed.”&lt;br /&gt;&lt;br /&gt;The challenge of the Exchange is to get more information flowing between broker and underwriter. This initiative is at the exact same point where others have failed and we have heard the same rallying cry from previous advocates of change. But how can you break through to the next level and actually get meaningful volumes of information being transmitted between trading partners?&lt;br /&gt;&lt;br /&gt;The answer is certainly not to ask the brokers to work harder or spend more money to make it happen. They will merely smile sweetly (again) and carry on with their own priorities.&lt;br /&gt;&lt;br /&gt;So, how do you break the cycle of failure? - &lt;strong&gt;Change the path of least resistance.&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;Today, brokers often use Word to generate the documents they need to negotiate a client’s risk. In doing so, they trust their support staff to be on top of the latest market reform initiatives and their company’s rules. And then, most of the really useful information ends up locked inside these Word documents.&lt;br /&gt;&lt;br /&gt;There is a growing recognition, however, that by using specialist document automation technology such as &lt;a href="http://www.exari.com/"&gt;Exari,&lt;/a&gt; brokers can improve turn-around times (documents produced in 80% less time) while ensuring greater accuracy and built-in compliance. Our broker clients tell us that it’s easier to use a structured mechanism for building their documents than relying upon the free form use of word processing.&lt;br /&gt;&lt;br /&gt;Using Exari, documents are “assembled” from the relevant sections, clauses, paragraphs and words that are applicable to the risk class. During that process, data is automatically being gathered in the background. It is that data that can be transformed into a message and sent to underwriters via the Exchange.&lt;br /&gt;&lt;br /&gt;Everyone wins - &lt;strong&gt;Brokers&lt;/strong&gt; get better documents faster; &lt;strong&gt;Underwriters &lt;/strong&gt;have to do less checking since there are fewer elements that can go wrong; &lt;strong&gt;Clients&lt;/strong&gt; get better service and the &lt;strong&gt;Exchange &lt;/strong&gt;builds up its message traffic.&lt;br /&gt;&lt;br /&gt;If you use a &lt;strong&gt;document assembly solution like Exari&lt;/strong&gt; to structure the creation of your documents at the beginning of the placement process you can break the Groundhog Day curse.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;em&gt;This post was guest authored by Martin Kett, Exari's VP of Insurance Client Development.&lt;/em&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-7867870956797179770?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/eBpjAfeM2NQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/7867870956797179770/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/11/breaking-groundhog-day-curse.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/7867870956797179770?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/7867870956797179770?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/eBpjAfeM2NQ/breaking-groundhog-day-curse.html" title="Breaking the &quot;Groundhog Day&quot; Curse" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/11/breaking-groundhog-day-curse.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4FRnk_eSp7ImA9WxNUFE4.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-5297846523136524478</id><published>2009-10-30T06:41:00.007-04:00</published><updated>2009-11-05T10:28:37.741-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-05T10:28:37.741-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Sales Contracts" /><category scheme="http://www.blogger.com/atom/ns#" term="Sales Compensation" /><category scheme="http://www.blogger.com/atom/ns#" term="sales" /><title>Too Much Sales Time Spent on Contracts</title><content type="html">“In many organizations, up to 25% of sales time is spent on contract-related issues,” states Tim Cummins on his blog &lt;a href="http://tcummins.wordpress.com/"&gt;Commitment Matters&lt;/a&gt;. Tim is president of the &lt;a href="http://www.iaccm.com/"&gt;IACCM&lt;/a&gt;, a non-profit organization that’s become the global forum for innovation in trading relationships and practices.&lt;br /&gt;&lt;br /&gt;This is astounding. As we emerge from a very deep recession (knock on wood as GDP came out positive this week), organizations around the world are struggling to do more with less and to close sales more quickly. How do you do this when 25% less time is spent selling or prospecting?&lt;br /&gt;&lt;br /&gt;An alternative to the manual, slow and risky process of creating contracts and sales documents such as NDAs and proposals, is to use document assembly/contract automation software. These solutions allow sales reps to create structured, approved sales documents on the fly by answering questions in a browser. These systems can integrate into the CRM system so the sales rep doesn’t have to re-enter data and all contract data can go back into the system. This allows the company to also manage, analyze and report on these contracts.&lt;br /&gt;&lt;br /&gt;Another interesting subject touched on by Cummins comes from a report by &lt;a href="http://www.csoinsights.com/"&gt;CSO Insights&lt;/a&gt; on Sales Compensation and Performance Management. It talks about how the recession has caused many sales reps to miss their quotas and to begin to push the boundaries of what is ethical. The report goes on to say that sales reps state that the biggest cause for losing business is the “competitor’s price and terms.”&lt;br /&gt;&lt;br /&gt;And this brings us full circle back to contract automation. If you automate your sales contracts and capture the data, you can control what the rep can do with the Ts &amp;amp; Cs and give them some controlled flexibility to negotiate on their own as well. You can also risk- rank your contracts and start to compensate your reps not only on revenue but on the value of the underlying contract to your company.&lt;br /&gt;&lt;br /&gt;Dow Jones &amp;amp; DLA Piper joined us for a webinar on this topic: "How sales teams can reduce the time and expense of closing deals by 50%" &lt;a href="http://www.exari.com/community/sales-document-automation-webinar.html"&gt;Download the recording now.&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-5297846523136524478?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/eyWNDulDWTs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/5297846523136524478/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/10/too-much-sales-time-spent-on-contracts.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5297846523136524478?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5297846523136524478?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/eyWNDulDWTs/too-much-sales-time-spent-on-contracts.html" title="Too Much Sales Time Spent on Contracts" /><author><name>Terry Lee</name><uri>http://www.blogger.com/profile/06200405442167754620</uri><email>tlee@exari.com</email><gd:extendedProperty name="OpenSocialUserId" value="17680476721617926609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/10/too-much-sales-time-spent-on-contracts.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUYAQX89eip7ImA9WxNVEkk.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-6784656699442492147</id><published>2009-10-22T09:21:00.016-04:00</published><updated>2009-10-22T16:25:40.162-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-22T16:25:40.162-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><title>Document Assembly Software Explained &amp; Reviewed</title><content type="html">Noted document assembly expert, Seth Rowland, has written a &lt;a href="http://bashasys.com/document-assembly/introduction/how-does-it-work.html"&gt;beginner's guide to Document Assembly&lt;/a&gt; that does a good job of explaining how &lt;strong&gt;document assembly software&lt;/strong&gt; works.&lt;br /&gt;&lt;br /&gt;Document Assembly goes by many different names, depending on the related job function and industry. It can be called document automation, document generation, contract automation, policy configuration, loan documentation, document creation and many more. For simplicity, we'll stick with document assembly here.&lt;br /&gt;&lt;br /&gt;Recently, Seth reviewed Exari Document Assembly Software in the TechnoFeature Newsletter. Below are some excerpts:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;In evaluating a document assembly system, one must look at what the user sees when he or she launches the document assembly interview. If the user's experience is "pleasant"; if the user can easily navigate the questions; if the user is guided to make the correct choices; and if the user can easily review and change his or her answers, then you can say that the system succeeds. &lt;strong&gt;The Exari interview shines in each of these areas&lt;/strong&gt;.&lt;br /&gt;&lt;/li&gt;&lt;br /&gt;&lt;li&gt;At the end of the interview, Exari presents you with several optional outputs including Word and PDF. The most interesting option is a document preview. You can see the document with variables and optional text indicated...Exari adds a further output option that is &lt;strong&gt;unique in the document assembly industry&lt;/strong&gt;. Called the Exari RoundTrip, it produces a Word document that can be negotiated and edited.&lt;br /&gt;&lt;/li&gt;&lt;br /&gt;&lt;li&gt;&lt;strong&gt;Exari has just about every feature you could imagine for a document assembly system&lt;/strong&gt;. Variables and various other components, just like documents, are stored as XML objects. Exari has variables, conditions, repeats, calculations, conditional expressions, multiple choice questions, and user text questions. To the standard list, Exari adds smart phrases, blocks of text that are reusable in the template and may or may not contain conditions, variables, and logic.&lt;br /&gt;&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Exari includes several other components that round it out as a robust and powerful programming language.&lt;br /&gt;&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Clearly, you'll need to conduct a return on investment analysis. Look at the number of users who will use the system, the number of documents they will assemble, the location of the users, and the level of expertise among the users regarding the documents. &lt;strong&gt;In the proper setting, Exari will pay for itself in under three months after full production&lt;/strong&gt;.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;You can read the &lt;a href="http://www.exari.com/images/press-coverage/rowland-document-assembly-system.pdf"&gt;complete review here&lt;/a&gt;. And please, let us know what you call Document Assembly below in the comments.&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-6784656699442492147?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/Egwm4gWoeQU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/6784656699442492147/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/10/document-assembly-software-explained.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/6784656699442492147?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/6784656699442492147?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/Egwm4gWoeQU/document-assembly-software-explained.html" title="Document Assembly Software Explained &amp; Reviewed" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/10/document-assembly-software-explained.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEAMQXY9fip7ImA9WxNWFk4.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-1309341312003865576</id><published>2009-10-15T14:53:00.000-04:00</published><updated>2009-10-15T14:53:00.866-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-15T14:53:00.866-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="contract management" /><category scheme="http://www.blogger.com/atom/ns#" term="law departments" /><title>The 4 key challenges of contract management for law departments</title><content type="html">Well known legal department consultant, Rees Morrison, reminds us of the &lt;a href="http://www.lawdepartmentmanagementblog.com/law_department_management/2009/10/contract-management-and-its-four-key-concerns-for-legal-departments.html"&gt;four key challenges contract management poses for in-house lawyers&lt;/a&gt;:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Standardizing and simplifying contract &lt;b&gt;drafting&lt;/b&gt;.&lt;/li&gt;&lt;li&gt;Setting policies regarding legal department &lt;b&gt;review&lt;/b&gt; of contracts.&lt;/li&gt;&lt;li&gt;Streamlining contract &lt;b&gt;negotiation&lt;/b&gt;.&lt;/li&gt;&lt;li&gt;Facilitating the company's &lt;b&gt;adherence&lt;/b&gt; to its contractual obligations.&lt;/li&gt;&lt;/ol&gt;Morrison notes the role of document assembly in addressing the drafting issue. Interestingly however, all four issues can actually benefit from a document assembly solution.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;1. Contract drafting&lt;/b&gt;&lt;br /&gt;Most legal departments try to improve contract drafting by using MS Word templates. However, these create problems for all parts of an organization:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Business users hate Word templates. Their eyes glaze over when they see square brackets and verbose user instructions. Instead, they either ask Legal to do the work, or they cut-and-paste from a previous agreement.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;The lawyers are unhappy too. Word templates are too risky. Often, business users can't get the substantive terms right and Legal has no visibility into the deal. &lt;/li&gt;&lt;/ul&gt;&lt;div&gt;In contrast, document assembly enables drafting to be pushed out to the business as a self-service model, while ensuring the generated agreements are legally compliant. The business users are guided through an intuitive web interview. The lawyers retain control by pre-determining what content is included.  Further, PDF output ensures that the business user can't modify the document post-production.&lt;/div&gt;&lt;br /&gt;&lt;b&gt;2. Contract review&lt;/b&gt;&lt;br /&gt;For legal departments with contract review policies in place, document assembly systems can  enforce those policies by embedding them into the system as rules.&lt;br /&gt;&lt;br /&gt;When there is non-compliance with a rule (e.g. in answer to an insurance question, a user might respond that the counter-party has insufficient insurance), the system automatically routes the contract to the legal department for review.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;3. Contract negotiation&lt;/b&gt;&lt;br /&gt;Document assembly can improve negotiation in two ways:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;By building commonly negotiated fall-back scenarios into the system (with different answers triggering the inclusion of particular provisions) the negotiation process is made much faster.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Some systems can actually capture all edits made to a document after it has been generated. That ensures any changes made by a counter-party are visible (even if MS Word Track Changes has not been used). Further, these negotiated positions can even be applied to subsequent agreements such as renewals.&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;4. Contract tracking&lt;/b&gt;&lt;br /&gt;Typically, there is both a functional- and system-separation at the point of contract execution. Pre-execution work (drafting, review and negotiation) is controlled by Legal, while post-execution tasks (obligation management) are usually handled by a contracts department or business unit.&lt;br /&gt;&lt;br /&gt;For companies that have implemented a contract management system, the right document assembly system can provide huge advantages via integration. They are able to:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Automatically push the execution version of an agreement into the contract management system in electronic form (even if the document has been heavily negotiated).&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Flag the extent to which clauses have been modified; which changes are simply approved fallback provisions, and which contain bespoke wording.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Enable analysis and reporting on the risk profile of an organization's entire contract portfolio.&lt;/li&gt;&lt;/ul&gt;&lt;b&gt;Conclusion&lt;/b&gt;&lt;br /&gt;Currently, a few innovative legal departments are realizing the full potential of document assembly. For various reasons, most organizations have not yet analyzed contracting the same ways they have other business processes. However, when they do, they will discover that the contracting process is highly inefficient, and that the potential cost savings from automation are just too great to ignore.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-1309341312003865576?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/nR6zVYjjlg0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/1309341312003865576/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/10/4-key-challenges-of-contract-management.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/1309341312003865576?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/1309341312003865576?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/nR6zVYjjlg0/4-key-challenges-of-contract-management.html" title="The 4 key challenges of contract management for law departments" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/10/4-key-challenges-of-contract-management.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYDRXY9fyp7ImA9WxNWFEk.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-2148285924278132635</id><published>2009-10-13T11:00:00.004-04:00</published><updated>2009-10-13T11:19:34.867-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-13T11:19:34.867-04:00</app:edited><title>Insurers improve productivity with KM</title><content type="html">It’s one thing for us to say that we can help you improve your business. It’s entirely different for you to hear it from someone who has already succeeded in making their own business more profitable.&lt;br /&gt;&lt;br /&gt;Les Doel, a manager at London-based Lloyd’s broker, Croton Stokes Wilson Ltd., recently spoke with &lt;a href="http://www.kmworld.com/Articles/Editorial/Feature/Insurers-improve-productivity-with-KM-56212.aspx"&gt;KM World Magazine&lt;/a&gt; about his experience with document automation.&lt;br /&gt;&lt;br /&gt;He said, "We wanted to be able to process more business with the same number of staff. The biggest challenge in becoming more productive was working with all of the different forms generated between Lloyd’s and various U.S. firms.”&lt;br /&gt;&lt;br /&gt;After testing different products, Les chose Exari InsuranceAccelerator™.&lt;br /&gt;&lt;br /&gt;You can read the &lt;a href="http://www.kmworld.com/Articles/Editorial/Feature/Insurers-improve-productivity-with-KM-56212.aspx"&gt;full article here&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-2148285924278132635?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/p_OB9MX-DJk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/2148285924278132635/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/10/insurers-improve-productivity-with-km.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2148285924278132635?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2148285924278132635?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/p_OB9MX-DJk/insurers-improve-productivity-with-km.html" title="Insurers improve productivity with KM" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/10/insurers-improve-productivity-with-km.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkUFRns_eCp7ImA9WxNXGU4.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-7831110169753804177</id><published>2009-10-07T12:49:00.001-04:00</published><updated>2009-10-07T12:50:17.540-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-07T12:50:17.540-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="processes" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><title>How to become an Automation Superhero</title><content type="html">Here's Justin's latest post from CIO.com. You can read it here or check it out along with those from other thought leaders over at &lt;a href="http://advice.cio.com/jlipton/how_to_become_an_automation_superhero?source=rss_Blogs_and_Discussion_All"&gt;CIO&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Many business processes have been streamlined through automation but the production of documents and documentation often seems to be neglected.&lt;br /&gt;We’re all aware of the benefits of automation. Our network monitoring, backups, integrity and heath checks, spam filtering, intrusion detection, software builds and unit tests are all largely automated. One area that often seems to be left out in the cold is the automation of documents and documentation.&lt;br /&gt;&lt;br /&gt;The &lt;a href="http://www.exari.com/solutions.html"&gt;document assembly/automation space &lt;/a&gt;has come a long way in the last decade particularly with systems that are founded on XML and are architected openly, enabling integration with necessary upstream and downstream systems. Clearly I’m biased; it’s what we at Exari have committed ourselves to for that past 10 years. Imagine what a superhero you could become in your company if you were able to achieve the following:&lt;br /&gt;&lt;br /&gt;Sales – a sales enquiry come in from your website. The lead wants more information. By filling in a simple, relevant online interview the prospect can potentially receive a customized business case or quote for your offering. It would be correctly branded, be up to date with the latest product information, pricing and discounts. An ROI analysis could be included based on the gathered information giving them even more compelling reasons to buy. Sample usage and support terms could also be delivered. Tell me that’s not going to excite your sales staff.&lt;br /&gt;&lt;br /&gt;Software configuration and documentation – Your lead has been converted and you’ve made the sale. They’ve paid for your software offering and are ready to have it installed and configured. Your product has a myriad of modules, configuration and installation options. An online interview combined with the previous sales information can gather information about the specific environments, required options and configuration parameters. From this you can deliver customized installation, configuration files and operation guides and potentially even the configured software itself.&lt;br /&gt;&lt;br /&gt;Legal – Do your product and service contracts still need to be approved by legal? Sure for unique, custom or ad hoc transactions legal needs to be deeply involved. But what about for standard deals – deals that are predictable and have a finite number of controlled variations? We all recognize that there are repeatable patterns around all common transactions. The business rules around these types of documents should be built into the document creation process . There should be a single source for such documents with up to date terms, pricing and conditions. Your business users should be able to generate these documents without legal intervention.&lt;br /&gt;&lt;br /&gt;So next time you start thinking about how you’re going to make an impact by improving business processes don’t forget about automating your documents.&lt;br /&gt;&lt;br /&gt;Where have you improved your business processes? Please let us know below in the comments.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-7831110169753804177?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/9RnDBP5v6Eg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/7831110169753804177/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/10/how-to-become-automation-superhero.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/7831110169753804177?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/7831110169753804177?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/9RnDBP5v6Eg/how-to-become-automation-superhero.html" title="How to become an Automation Superhero" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/10/how-to-become-automation-superhero.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcDR3ozeCp7ImA9WxNXFEQ.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-1127319512335542209</id><published>2009-10-02T00:36:00.010-04:00</published><updated>2009-10-02T09:27:56.480-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-02T09:27:56.480-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="salesforce.com" /><category scheme="http://www.blogger.com/atom/ns#" term="lawyers" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="law departments" /><category scheme="http://www.blogger.com/atom/ns#" term="contract drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="sales" /><category scheme="http://www.blogger.com/atom/ns#" term="law firms" /><title>Dow Jones and DLA Piper webinar recording now available for download</title><content type="html">Do you work in a large company or law firm? If so, be sure to &lt;a href="http://bit.ly/CdyD6"&gt;download the webinar recording&lt;/a&gt; on how Dow Jones and DLA Piper have benefited (in quite different ways) by automating the sales contracting process.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Mitch Mackler, Assistant General Counsel at Dow Jones, gives a fascinating account of the results achieved by the salespeople and in-house lawyers at this iconic media company.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Dave Jensen, Director of IT at DLA Piper, explains how technology innovation at one of the world's largest law firms won them a highly valuable global client.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;&lt;a href="http://bit.ly/CdyD6"&gt;&lt;b&gt;&lt;span class="Apple-style-span" style="TEXT-DECORATION: none"&gt;Download the webinar recording now&lt;/span&gt;&lt;/b&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-1127319512335542209?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/btkD5bEkmIM" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/1127319512335542209/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/10/dow-jones-and-dla-piper-webinar.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/1127319512335542209?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/1127319512335542209?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/btkD5bEkmIM/dow-jones-and-dla-piper-webinar.html" title="Dow Jones and DLA Piper webinar recording now available for download" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/10/dow-jones-and-dla-piper-webinar.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkEGQ3w-eSp7ImA9WxNQGUw.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-1173945558472893622</id><published>2009-09-25T16:09:00.010-04:00</published><updated>2009-09-25T16:30:22.251-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-25T16:30:22.251-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="word" /><title>The Perils of MS Word</title><content type="html">Our Chief Technology Officer (CTO) Justin Lipton has begun blogging over at &lt;a href="http://advice.cio.com/"&gt;CIO.com. &lt;/a&gt;From time to time we’ll share Justin’s posts in this blog as well. Here’s his most recent:&lt;br /&gt;&lt;br /&gt;A mistake in a Word document has caused considerable damage and embarrassment to a publicly listed company in New Zealand. I recently read this &lt;a href="http://www.nzx.com/markets/NZSX/NZS/announcements/2806777/NZ-Farming-Systems-Uruguay-Ltd-Annual-Financial-Statement"&gt;post&lt;/a&gt; about an unfortunate comment that was left in a company’s annual financial statement. It reminded me how careful we need to be when using generic tools such as Word to produce documents. Here are some tips for how to avoid this kind of embarrassment:&lt;br /&gt;&lt;br /&gt;Read it before you send it – OK this is really obvious but if you’ve created a document using cut and paste there’s a very good chance it will contain something you don’t want it to. That includes notes and comments too. After you’ve read it, read it again and if it’s important give it to someone else to read and review.&lt;br /&gt;&lt;br /&gt;Word metadata – Metadata is often neglected but it can contain the original author, path, company etc. If you’ve ever based one document on another or used a template that wasn’t created by you this can really bite – particularly if the metadata identifies another client or worse still a competitor. Many companies even have Word macros to strip the metadata out of Word docs when they are opened.&lt;br /&gt;&lt;br /&gt;Track changes – "just because you can’t see it doesn’t mean it’s not there." Tracking changes is great – it allows you to see how a document evolves: who made changes, what changes and when. Do you really want non-trusted people to see this too? Before sending a document always ensure that track changes is turned off and that all changes have been accepted.&lt;br /&gt;&lt;br /&gt;Fast saves – you may not realize this but later versions of Word have a history feature. With this enabled you can see different versions of your document as you were editing it. OK for you – not so great for the non-trusted recipient who ends up seeing something potentially embarrassing to both you and your company.&lt;br /&gt;&lt;br /&gt;And finally, don’t use Word output unless you have to. Use Word for writing and editing ad hoc documents but PDF is superior as a final format. Sometimes this may be impractical, but use PDFs whenever you can. For common documents utilize document assembly tools to make your life that much easier and safer.&lt;br /&gt;&lt;br /&gt;What tips can you share to help others avoid such perils? Please share in the comments.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-1173945558472893622?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/Ls5ewcjp9Ec" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/1173945558472893622/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/09/perils-of-ms-word.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/1173945558472893622?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/1173945558472893622?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/Ls5ewcjp9Ec/perils-of-ms-word.html" title="The Perils of MS Word" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/09/perils-of-ms-word.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkcGRns7fSp7ImA9WxNXFEg.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-3838225754216008704</id><published>2009-09-18T13:29:00.029-04:00</published><updated>2009-10-02T00:33:47.505-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-02T00:33:47.505-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="salesforce.com" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="sales" /><title>Contract Automation Impacts the Sales Cycle</title><content type="html">As technology and the economy have created more and more pressure to close deals faster with less cost, innovative sales executives are looking for ways to &lt;a href="http://www.exari.com/salesaccelerator.html"&gt;accelerate their sales cycle &lt;/a&gt;without increasing headcount and costs.&lt;br /&gt;&lt;br /&gt;Contract automation not only saves time in contract creation but can also eliminate the need to wait for a busy legal department to create and review contracts. Inefficient, manual processes waste time and money throughout the enterprise.&lt;br /&gt;&lt;br /&gt;Dow Jones and DLA Piper have both experienced firsthand success with document automation and they are sharing their know-how.&lt;br /&gt;&lt;br /&gt;Join us for a webinar on Thursday, September 24 at 1:00 pm (EDT) to learn how:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Dow Jones has reduced the time it takes their salespeople to get a first draft contract to their customer down from several days to one half-hour, regardless of where they are located, or whether the lawyer normally assigned to them is otherwise engaged.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;DLA Piper has helped their clients to streamline contracting processes and reduce the time and expense that is required for these types of activities.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;To empower sales staff to create their own compliant contracts in minutes and leverage Salesforce.com.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;a href="http://exari.web101.hubspot.com/salesaccelerator-webinar/?utm_campaign=SalesAccelerator-Webinar-Sep-09"&gt;Register here to attend the Webinar.&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Not available on the 24th? &lt;a href="http://www.exari.com/community/library-webinars.html"&gt;Register here to receive the recording.&lt;/a&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-3838225754216008704?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/OUGfK4NGKN4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/3838225754216008704/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/09/contract-automation-impacts-sales-cycle.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/3838225754216008704?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/3838225754216008704?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/OUGfK4NGKN4/contract-automation-impacts-sales-cycle.html" title="Contract Automation Impacts the Sales Cycle" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/09/contract-automation-impacts-sales-cycle.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak4GRXs9fip7ImA9WxNREEo.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-5370727216826205966</id><published>2009-09-04T11:27:00.016-04:00</published><updated>2009-09-04T11:42:04.566-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-04T11:42:04.566-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="reinsurance" /><category scheme="http://www.blogger.com/atom/ns#" term="insurance" /><category scheme="http://www.blogger.com/atom/ns#" term="certainty" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><title>Document Assembly for Insurance Policy Generation</title><content type="html">Although document assembly has its origins in the world of law firms and legal contracts, it has more recently been pressed into service as a document automation platform in the document-intensive insurance world. After all, an insurance or reinsurance policy is indeed a contract.&lt;br /&gt;&lt;br /&gt;The need for contract certainty along with increased scrutiny from the regulators, and growing pressure for cost savings, makes document assembly an ideal insurance industry solution.&lt;br /&gt;&lt;br /&gt;Exari has helped many insurance brokers, underwriters and carriers to automate their documents, most recently, &lt;a href="http://www.exari.com/media-releases/mr20090901.html"&gt;Munich Re&lt;/a&gt;. Munich Re’s UK Life Branch has automated their Treaty Contracts. The company believes the efficiencies achieved through this document automation project will help them lower costs and offer even better customer service.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.exari.com/forms/contact-us.html"&gt;Contact us &lt;/a&gt;to learn how we can help you with your insurance document automation needs.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-5370727216826205966?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/KOer9DrwVpY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/5370727216826205966/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/09/document-assembly-for-insurance-policy.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5370727216826205966?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5370727216826205966?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/KOer9DrwVpY/document-assembly-for-insurance-policy.html" title="Document Assembly for Insurance Policy Generation" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/09/document-assembly-for-insurance-policy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8CRnw7cSp7ImA9WxNSE0k.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-2397049181174488834</id><published>2009-08-26T19:07:00.024-04:00</published><updated>2009-08-26T23:47:47.209-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-26T23:47:47.209-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="technology" /><category scheme="http://www.blogger.com/atom/ns#" term="time" /><category scheme="http://www.blogger.com/atom/ns#" term="innovation" /><category scheme="http://www.blogger.com/atom/ns#" term="future" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><category scheme="http://www.blogger.com/atom/ns#" term="contract drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="law firms" /><title>10 technologies that will disrupt traditional legal practice</title><content type="html">At ILTA '09 yesterday, Ron Friedmann '&lt;a href="http://www.prismlegal.com/wordpress/index.php?m=200908#post-990"&gt;live blogged&lt;/a&gt;' (no, I didn't just invent &lt;a href="http://en.wiktionary.org/wiki/live_blogged"&gt;that term&lt;/a&gt;) a panel discussion on &lt;i&gt;Technologies That Will Disrupt Traditional Legal Practice&lt;/i&gt;, lead by &lt;a href="http://www.susskind.com/"&gt;Richard Susskind&lt;/a&gt;. By all accounts, the session was very well received. Below is my take on some of Susskind's key points. (If you're interested in the future of legal practice I urge you to &lt;a href="http://www.prismlegal.com/wordpress/index.php?m=200908#post-990"&gt;read Ron's full post&lt;/a&gt;.)&lt;div&gt;&lt;b&gt;&lt;/b&gt;&lt;/div&gt;&lt;blockquote&gt;&lt;div&gt;&lt;b&gt;What is disruptive technology?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;In contrast to sustaining technology, disruptive technology seems to come from nowhere and disrupts the market. It's not the technology itself that's interesting, but rather its potential impact on existing business models (such as the billable hour).&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-weight: bold; "&gt;Is it a threat or opportunity?&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;That, of course, depends on who you are. It provides an opportunity for innovators and customers, but is a threat for those that want to maintain the status quo. Susskind notes that law firms tend to be in the latter camp.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;What is the role of document assembly?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Susskind's view is that document assembly, along with other technologies, will transform the legal market over the coming years.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;However, rather than internal document assembly (which many firms have had 20+ years' experience with), he sees the real opportunity in external (i.e. client-facing) online services. It's here that the economics are stronger as the volume of documents produced can be much higher.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;And it's disruptive because 1) it requires an upfront investment of time and money, and 2) when a document is produced by the system its value isn't tied to the time required to generate it. &lt;i&gt;[As noted by another attendee, &lt;/i&gt;&lt;a href="http://caselines.blogspot.com/2009/08/ilta-09-panel-technologies-that-will.html"&gt;&lt;i&gt;David Hobbie&lt;/i&gt;&lt;/a&gt;&lt;i&gt;, "it takes the lawyers out of the business of producing documents."]&lt;/i&gt;&lt;/div&gt;&lt;/blockquote&gt;&lt;div&gt;&lt;i&gt;&lt;/i&gt;&lt;/div&gt;&lt;div&gt;To learn about the other nine disruptive technologies mentioned by Susskind, and the law firm case studies presented by &lt;a href="http://www.bryancave.com/jialber/"&gt;John Alber of Bryan Cave&lt;/a&gt; and &lt;a href="http://www.mallesons.com/Our_firm/9169208W.htm"&gt;Gerard Neiditsch of Mallesons&lt;/a&gt;, read the full posts from &lt;a href="http://www.prismlegal.com/wordpress/index.php?m=200908#post-990"&gt;Ron&lt;/a&gt; and &lt;a href="http://caselines.blogspot.com/2009/08/ilta-09-panel-technologies-that-will.html"&gt;David&lt;/a&gt;.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;To find out how document assembly can help strengthen your firm's market position &lt;a href="http://www.exari.com/forms/contact-us.html"&gt;contact Exari&lt;/a&gt;.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-2397049181174488834?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/bO72LIe6Kck" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/2397049181174488834/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/08/10-technologies-that-will-disrupt.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2397049181174488834?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2397049181174488834?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/bO72LIe6Kck/10-technologies-that-will-disrupt.html" title="10 technologies that will disrupt traditional legal practice" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/08/10-technologies-that-will-disrupt.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8BRno5eCp7ImA9WxNSE0w.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-5545769228362358558</id><published>2009-08-26T15:57:00.004-04:00</published><updated>2009-08-26T16:00:57.420-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-26T16:00:57.420-04:00</app:edited><title>The Assault on the Billable Hour Back in the News</title><content type="html">The Billable Hour is still under attack in the nation’s press and real change seems to be taking hold.  According to several recent blog posts and the Wall Street Journal, corporations are using the recession to structurally change the way they acquire legal services. &lt;br /&gt;&lt;br /&gt;Document Assembly is one technology amongst many that can increase the efficiency and productivity of a corporation by automating high volume documents such as sales contracts, services agreements, licensing agreements, etc, AND of a law firm by accelerating the speed of complex document creation.  This increased efficiency drives lower and more predictable costs that can then allow law firms to remain profitable in a fixed price environment.&lt;br /&gt;&lt;br /&gt;In the &lt;a href="http://online.wsj.com/article/SB125106954159552335.html"&gt;Wall Street Journal Nathan Koppel and Ashby Jones &lt;/a&gt;wrote about U.S. corporations pushing their outside counsels for flat fee contracts.&lt;br /&gt;&lt;br /&gt;“The companies are ditching the hourly structure -- which critics complain offers law firms an incentive to rack up bigger bills -- in favor of flat-fee contracts. One survey found an increase of more than 50% this year in corporate spending on alternatives to the traditional hourly-fee model.”  Pfizer, American Express and Cisco are all cited in the article has having done very creative fixed price deals with the outside law firms they use.&lt;br /&gt;&lt;a href="http://www.minnlawyer.com/article.cfm/2009/08/24/Flat-fees-a-growing-trend-among-firms-big-and-small"&gt;&lt;br /&gt;“Flat fees a growing trend among firms big and small" in the Minnesota Lawyer&lt;/a&gt; by Associate Editor Michelle Lore states that “St. Louis lawyer, writer, speaker and entrepreneur Matthew Homann believes that any case can be priced on a flat-fee basis if the attorney has the experience to properly evaluate the matter and has the systems in place to handle it economically.”   Mr. Homann also has a blog about this subject called&lt;a href="http://thenonbillablehour.typepad.com/"&gt; “The [non]billable hour”&lt;/a&gt;.&lt;br /&gt;&lt;a href="http://www.rolandschorr.com/blogs/index.php/2009/08/24/the-billable-hour-under-attack?blog=6"&gt;&lt;br /&gt;Law Office Technology by Roland Schorr &amp;amp; Tower&lt;/a&gt;, talks about how technology can help law firms bridge the gap between the billable hour and fixed pricing.  "Tech can bring efficiencies. Ironically firms have long been wary of technology specifically BECAUSE of the billable hour. If you use document assembly software that cuts your time to compose a particular document down from 3 hours to 1 hour...well, you've just cost yourself TWO billable hours! But in a value-based system, that's a GOOD thing.”&lt;br /&gt;&lt;br /&gt;It’s not news to us that good use of good technology brings efficiency.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-5545769228362358558?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/8rheu1CaEqc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/5545769228362358558/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/08/assault-on-billable-hour-back-in-news_26.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5545769228362358558?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5545769228362358558?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/8rheu1CaEqc/assault-on-billable-hour-back-in-news_26.html" title="The Assault on the Billable Hour Back in the News" /><author><name>Terry Lee</name><uri>http://www.blogger.com/profile/06200405442167754620</uri><email>tlee@exari.com</email><gd:extendedProperty name="OpenSocialUserId" value="17680476721617926609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/08/assault-on-billable-hour-back-in-news_26.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0EAR387cSp7ImA9WxNTF0U.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-672961602900170461</id><published>2009-08-20T12:25:00.002-04:00</published><updated>2009-08-20T12:27:26.109-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-20T12:27:26.109-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><title>Five Document Assembly/Legal Technology Blogs to Follow</title><content type="html">If you are interested in document assembly and other legal technologies, which you probably are since you are reading this, here are some other blogs you may want to check out:&lt;br /&gt;&lt;a href="http://bashasys.info/index.php"&gt;&lt;/a&gt;&lt;br /&gt;&lt;a href="http://bashasys.info/"&gt;Basha Blog&lt;/a&gt;&lt;br /&gt;Seth Rowland is a nationally recognized industry expert on document assembly. He runs a technology consulting practice that helps clients use software to redesign the legal document drafting process. He writes about document assembly and case management.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.adamsdrafting.com/"&gt;AdamsDrafting&lt;/a&gt;&lt;br /&gt;Ken Adams is a leading authority on modern and effective contract drafting. He is the author of "A Manual of Style for Contract Drafting."&lt;br /&gt;&lt;br /&gt;&lt;a href="http://denniskennedy.com/blog/"&gt;DennisKennedy.com&lt;/a&gt;&lt;br /&gt;Dennis Kennedy is a well-known lawyer, consultant, speaker and writer who is considered among the most influential authority on the application of technology in the practice of law.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://lawdepartmentmanagement.typepad.com/"&gt;Law Department Management&lt;/a&gt;&lt;br /&gt;Rees Morrison, Esq., has consulted to more than 275 law departments over 22 years to help them better manage themselves and their law firms. Rees does include, though is not limited to technology issues.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://doesitcompute.typepad.com/"&gt;Does it Compute?&lt;/a&gt;&lt;br /&gt;John Heckman has worked in the legal industry for nearly 25 years. He consults with firms from solo practitioners to AmLaw 100 firms, and he specializes in Document Management issues.&lt;br /&gt;&lt;br /&gt;What blogs would you add to this list?&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-672961602900170461?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/7ZWFLzXW71U" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/672961602900170461/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/08/five-document-assemblylegal-technology.html#comment-form" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/672961602900170461?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/672961602900170461?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/7ZWFLzXW71U/five-document-assemblylegal-technology.html" title="Five Document Assembly/Legal Technology Blogs to Follow" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total><feedburner:origLink>http://blog.exari.com/2009/08/five-document-assemblylegal-technology.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04CQHk6cCp7ImA9WxNTEEU.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-483832419029706482</id><published>2009-08-12T11:11:00.004-04:00</published><updated>2009-08-12T11:12:41.718-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-12T11:12:41.718-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="xml based document automation" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation technologies" /><title>MS Word is dead, long live MS Word</title><content type="html">Exari CTO Justin Lipton recently wrote about the potential demise of MS Word on the &lt;a href="http://advice.cio.com/jlipton/ms_word_is_dead_long_live_ms_word"&gt;CIO blog&lt;/a&gt; after reading this &lt;a href="http://arstechnica.com/microsoft/news/2009/08/microsoft-word-1983---2009-rest-in-peace.ars"&gt;article&lt;/a&gt;. In case you missed it, we are reposting it here.&lt;br /&gt;&lt;br /&gt;Sure Word is bloated and many of the features are difficult to use or are never used, but it's hard to be beat for producing ad-hoc documents.&lt;br /&gt;&lt;br /&gt;The article argues that where collaboration is required, web based authoring tools such as wikis and deal rooms provide much better solutions.But there's a part of the argument missing that applies as much to a wiki as it does to any unstructured document.&lt;br /&gt;&lt;br /&gt;Most documents that contains useful information should be able to be separated into a data payload component, a text component and a style component.The data component consists of the dates, amounts, milestones, names, places, conditions, exceptions, etc that the document relates to. This is the key to tracking, reporting and analyzing a document.&lt;br /&gt;&lt;br /&gt;The text is the specific wording that goes around the data - this generally requires a human to completely understand the meaning.&lt;br /&gt;&lt;br /&gt;Finally, the style is the way the document looks.&lt;br /&gt;&lt;br /&gt;XML based document assembly/automation technologies allow for a distinct separation of these three facets. There's really no excuse with the technologies available today to be writing commonly used documents from scratch or cutting and pasting from various sources. Important documents should be available as single sourced, marked up templates that require very little effort to produce, are beautifully formatted and are able to be easily analyzed and reported on.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;em&gt;&lt;u&gt;&lt;span style="color:#0000ff;"&gt;&lt;/span&gt;&lt;/u&gt;&lt;/em&gt;&lt;/strong&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-483832419029706482?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/rU6Wsx5oRbk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/483832419029706482/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/08/ms-word-is-dead-long-live-ms-word.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/483832419029706482?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/483832419029706482?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/rU6Wsx5oRbk/ms-word-is-dead-long-live-ms-word.html" title="MS Word is dead, long live MS Word" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://blog.exari.com/2009/08/ms-word-is-dead-long-live-ms-word.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QEQHw4cSp7ImA9WxJaFE0.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-5019126674217382584</id><published>2009-07-30T17:02:00.012-04:00</published><updated>2009-08-04T11:55:01.239-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-04T11:55:01.239-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="intelligent document assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><category scheme="http://www.blogger.com/atom/ns#" term="contract drafting" /><title>What’s your greatest weakness in contract drafting?</title><content type="html">&lt;p&gt;Sinning, we know, is human. And we all know what Capital Vices are. But no one before has applied the 7 Deadly Sins to contract drafting, and explained how common errors in writing legal agreements can lead to “eternal contractual damnation”.&lt;/p&gt;&lt;p&gt;Jamie Wodetzki, Founder of Exari, did. Led by his experience in document automation – just like Dante was led by Virgil – Jamie starts a fascinating trip to investigate the 7 Cardinal Sins with a focus on contract drafting. He walks us through the most common mistakes that lawyers and professionals make when writing contracts and legal documents, and explores the solutions provided by intelligent document assembly to cut costs and eliminate risk.&lt;/p&gt;&lt;p&gt;Originally presented as a Technology Session at Legal Tech 2009, this interesting and timely presentation is now available in &lt;a href="http://www.exari.com/community/document-automation-video-gallery.html"&gt;seven free 2-minute clips on the Exari website&lt;/a&gt;, and includes stories from the front line of legal service automation at leading companies and law firms around the world.&lt;/p&gt;&lt;p&gt;Here is Jamie’s list of don’ts:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;a href="http://www.youtube.com/watch?v=lxDmj1KxiKU"&gt;Lust&lt;/a&gt;: Don’t lust after sexy documents and be obsessed by beautiful fonts.&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.youtube.com/watch?v=P1f-LooIrG8"&gt;Gluttony&lt;/a&gt;: Don’t draft fat, excessively long contracts.&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.youtube.com/watch?v=STLSSvuWcBc"&gt;Greed&lt;/a&gt;: Don’t write take-it-or-leave-it, one-sided standard form contracts.&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.youtube.com/watch?v=MCc4bd9Krgk"&gt;Sloth&lt;/a&gt;: Don’t make mistakes due to inaccurate, lazy drafting.&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.youtube.com/watch?v=rb-5QOfXvo8"&gt;Wrath&lt;/a&gt;: Don’t be caught with the wrong clauses and get aggressive.&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.youtube.com/watch?v=esupINONc1o"&gt;Envy&lt;/a&gt;: Don’t fail to focus on details, as well as the big things.&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.youtube.com/watch?v=pyyTCQjUVRA"&gt;Pride&lt;/a&gt;: Don’t find yourself guilty of excessive love for your own drafting. &lt;/li&gt;&lt;/ol&gt;&lt;p&gt;The 7 Deadly Sins of Contract Drafting teaches us that a little bit of sinning is acceptable, but in a global financial crisis the cost of sinning blows up and smart companies must be able to avoid such common mistakes and have complete visibility into their contracts. &lt;/p&gt;&lt;p&gt;&lt;a href="http://www.exari.com/community/document-automation-video-gallery.html"&gt;Check it out and tell us: what is your sin?&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;em&gt;This post was guest authored by Federica Ionta&lt;/em&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-5019126674217382584?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/jeK3igV5_sw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/5019126674217382584/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/07/whats-your-greatest-weakness-in.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5019126674217382584?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5019126674217382584?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/jeK3igV5_sw/whats-your-greatest-weakness-in.html" title="What’s your greatest weakness in contract drafting?" /><author><name>Adine Deford</name><uri>http://www.blogger.com/profile/12023998893252043625</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="00173981659743734771" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/07/whats-your-greatest-weakness-in.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkUNSXw4eCp7ImA9WxJbGEg.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-2280380751261434346</id><published>2009-07-29T02:02:00.001-04:00</published><updated>2009-07-29T02:51:38.230-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-29T02:51:38.230-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="data" /><category scheme="http://www.blogger.com/atom/ns#" term="compliance" /><category scheme="http://www.blogger.com/atom/ns#" term="lawyers" /><category scheme="http://www.blogger.com/atom/ns#" term="drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="risk" /><category scheme="http://www.blogger.com/atom/ns#" term="contracts" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="bottlenecks" /><category scheme="http://www.blogger.com/atom/ns#" term="law departments" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><category scheme="http://www.blogger.com/atom/ns#" term="agreement" /><title>3 signs you should automate your contracts</title><content type="html">If you manage a corporate legal department, there are three telltale signs that you might get significant value from automating the creation of your day-to-day business contracts.&lt;div&gt;&lt;ol&gt;&lt;li&gt;&lt;b&gt;Internal clients "work around" Legal&lt;br /&gt;&lt;/b&gt;&lt;br /&gt;If contracting is being done by people in the business without Legal's knowledge, the company is being exposed to unacceptable risks. Why do they feel the need to circumvent Legal? What can be done to remove the incentive?&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;span class="Apple-style-span" style="font-weight: bold; "&gt;All transactions must go via Legal&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Another problem is if Legal is drafting and reviewing routine agreements. It's an awful waste of highly skilled legal resources. Lawyers find the work tedious (cutting-and-pasting from a variety of templates and previous agreements, fixing broken auto-numbering, etc). Not to mention the frustration for internal clients caused by slow turnaround times. Why are routine documents being drafted by Legal? Is it because you don't trust the business? Do they not trust themselves?&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;span class="Apple-style-span" style="font-weight: bold; "&gt;Work is being outsourced to law firms&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;When Legal's too busy, it uses panel lawyers as an overflow. While this helps with the workload, it's an extremely expensive way of scaling. Is this really the most cost-effective way to provide legal services for your company?&lt;/li&gt;&lt;/ol&gt;&lt;b&gt;How automation can help&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/div&gt;&lt;div&gt;Automation makes it easy for your internal clients to follow approved processes. As a result, they're happy to comply. They're presented with an intuitive web-wizard containing business-friendly interview questions.&lt;/div&gt;&lt;div&gt;&lt;ul&gt;&lt;li&gt;&lt;b&gt;Standard transactions&lt;/b&gt;, - after answering the questions, clients get auto-generated, execution ready documents (in PDF format) tailored to their requirements. Instant access to legally pre-approved documents allows them to quickly "get on with business."&lt;/li&gt;&lt;li&gt;&lt;span class="Apple-style-span" style="font-weight: bold; "&gt;Non-standard transactions&lt;/span&gt; - by the same token, higher risk or more complex deals are automatically flagged and routed to Legal for review (in Word format).&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div&gt;The best thing is that you're now able to track all the company's agreements, and gain deep visibility into the types of transactions being entered into by the business. It also frees the legal team up to focus on value-added work. Which means that less stuff needs to be sent out to expensive external lawyers.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Automating contract drafting enables you to cut costs and reduce risk, while also being more responsive to your internal clients. Happy internal clients; happy legal team; happy finance department. A win-win-win.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-2280380751261434346?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/TOS6E2nb9ME" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/2280380751261434346/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/07/3-signs-you-should-automate-your.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2280380751261434346?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2280380751261434346?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/TOS6E2nb9ME/3-signs-you-should-automate-your.html" title="3 signs you should automate your contracts" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/07/3-signs-you-should-automate-your.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUMHR3g4eip7ImA9WxJbEEs.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-8201796608047429365</id><published>2009-07-16T20:22:00.019-04:00</published><updated>2009-07-20T00:17:16.632-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-20T00:17:16.632-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="word" /><category scheme="http://www.blogger.com/atom/ns#" term="formatting" /><category scheme="http://www.blogger.com/atom/ns#" term="lawyers" /><category scheme="http://www.blogger.com/atom/ns#" term="drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="tips" /><category scheme="http://www.blogger.com/atom/ns#" term="styles" /><category scheme="http://www.blogger.com/atom/ns#" term="document" /><title>Drafting contracts with style(s)</title><content type="html">&lt;div&gt;My post on &lt;a href="http://blog.exari.com/2009/06/drafting-contracts-to-be-understood.html"&gt;drafting contracts to be understood&lt;/a&gt; mentions the importance of typography (the layout and appearance of printed material) for clear communication. In a recent post, lawyer Sam Glover reinforces the point with &lt;a href="http://lawyerist.com/2009/07/09/legal-writing-make-yourself-understood-by-making-your-writing-easier-to-read/"&gt;five typography tips for lawyers&lt;/a&gt;. But it's Sam's sixth tip, a non-typographical one, that I'm most interested in.&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;/div&gt;&lt;blockquote&gt;&lt;div&gt;&lt;b&gt;&lt;i&gt;"Learn styles&lt;/i&gt;&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;i&gt;&lt;br /&gt;&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;i&gt;Manual formatting is clumsy, requires more effort, and yields inconsistent results. Learn to use styles, so that all your headings are formatted consistently, and so that you can change them all, if necessary, by changing only the style definition."&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;/blockquote&gt;&lt;div&gt;Lawyers spend a great deal of time editing and tweaking documents. And styling has a huge impact on how quickly a document's layout can be updated. So, if you're a lawyer, you owe it to yourself and your clients to invest some time in understanding how to use styles.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Fine, but where do I start?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;As well as the &lt;a href="http://office.microsoft.com/en-us/word/HA011876141033.aspx"&gt;Microsoft tutorial&lt;/a&gt; mentioned in Sam's post, I highly recommend Shauna Kelly's &lt;a href="http://www.shaunakelly.com/word/index.html"&gt;MS Word tutorials&lt;/a&gt;. (Anyone who's been hit with Word numbering mishaps will be particularly interested in Shauna's excellent &lt;a href="http://www.shaunakelly.com/word/numbering/OutlineNumbering.html"&gt;outline numbering tutorial&lt;/a&gt;.)&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-8201796608047429365?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/5YcZLvhdWfc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/8201796608047429365/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/07/drafting-contracts-with-styles.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/8201796608047429365?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/8201796608047429365?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/5YcZLvhdWfc/drafting-contracts-with-styles.html" title="Drafting contracts with style(s)" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/07/drafting-contracts-with-styles.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUUBQXc5eyp7ImA9WxJUEkw.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-8509514982199428842</id><published>2009-07-09T20:19:00.014-04:00</published><updated>2009-07-10T05:14:10.923-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-10T05:14:10.923-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="processes" /><category scheme="http://www.blogger.com/atom/ns#" term="employment" /><category scheme="http://www.blogger.com/atom/ns#" term="technology" /><category scheme="http://www.blogger.com/atom/ns#" term="relationships" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="Exari" /><category scheme="http://www.blogger.com/atom/ns#" term="CRM" /><category scheme="http://www.blogger.com/atom/ns#" term="business" /><title>Exari's customer, staff and business philosophies</title><content type="html">&lt;div&gt;Company culture is heavily influenced by the views of its leaders, particularly the people who've been around since 'Day 1'. Exari co-founder and Chief Technology Officer, Dr Justin Lipton, is one such person.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Juz recently started blogging over at &lt;a href="http://advice.cio.com/"&gt;CIO&lt;/a&gt;. So, I've decided to review some of his posts to provide insight into aspects of Exari's approach to doing business.&lt;/div&gt;&lt;blockquote&gt;&lt;div&gt;&lt;b&gt;Eating your own dog food&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;For us, that means using the Exari document assembly platform internally for all manner of template automation. Why? One reason is to help everyone in the company to better understand things from the customer perspective. (&lt;a href="http://advice.cio.com/jlipton/eating_your_own_dog_food"&gt;Read the post&lt;/a&gt;)&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Walking the walk&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;At Exari Juz (and other senior execs) get their hands dirty by regularly taking support calls, doing coding, and helping with other front-line work. The aim here is to gain first-hand experience of the issues faced by the majority of our staff. (&lt;a href="http://advice.cio.com/jlipton/walking_the_walk"&gt;Read the post&lt;/a&gt;)&lt;/div&gt;&lt;/blockquote&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;&lt;/span&gt;&lt;/div&gt;&lt;blockquote&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-weight: bold;"&gt;What the CEO tells you and what she's really saying&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;This is a lighthearted look at the disconnect that sometimes exists between the CIO and the CEO. The lesson for me is that clear communication is extremely important. That can be a challenge for distributed companies like ours (with offices in the US, Europe and Asia, we're spread across 14 times zones). One way we try to overcome the 'tyranny of distance' is by having weekly inter-office web/phone conferences; even when there is no formal agenda. (&lt;a href="http://advice.cio.com/jlipton/what_the_ceo_tells_you_and_what_hes_really_saying"&gt;Read the post&lt;/a&gt;)&lt;/div&gt;&lt;/blockquote&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;In a nutshell, at Exari we think it's really important to make sure we're on the same page as all our stakeholders (gotta love that work) by maintaining regular contact and also by 'walking a mile in their shoes.'&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;You can read more of &lt;a href="http://advice.cio.com/user/jlipton/track"&gt;Juz's musings over at CIO&lt;/a&gt;.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;i&gt;(P.S. Juz hates the 'Dr' prefix that denotes his PhD credentials; which is precisely why I included it in the intro ;-)&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;&lt;/b&gt;&lt;/div&gt;&lt;blockquote&gt;&lt;/blockquote&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-8509514982199428842?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/g2sGyn3NYkQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/8509514982199428842/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/07/exaris-customer-staff-and-business.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/8509514982199428842?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/8509514982199428842?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/g2sGyn3NYkQ/exaris-customer-staff-and-business.html" title="Exari's customer, staff and business philosophies" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/07/exaris-customer-staff-and-business.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0AFRnc-eyp7ImA9WxJUEEg.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-7003746566979251742</id><published>2009-07-08T06:31:00.013-04:00</published><updated>2009-07-08T08:21:57.953-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-08T08:21:57.953-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="processes" /><category scheme="http://www.blogger.com/atom/ns#" term="technology" /><category scheme="http://www.blogger.com/atom/ns#" term="contract management" /><category scheme="http://www.blogger.com/atom/ns#" term="contracts" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="analysts" /><title>Tim Cummins on what's holding back  contract lifecycle automation</title><content type="html">Predicting the future is a mug's game.&lt;br /&gt;&lt;br /&gt;In 2002 &lt;a href="http://www.gartner.com/5_about/press_releases/2002_05/pr20020521b.jsp"&gt;Gartner predicted&lt;/a&gt; that, by 2007, there would be a $20 billion market for Contract Lifecycle Management software and services.&lt;br /&gt;&lt;br /&gt;Tim Cummins - CEO of the International Association for Contract &amp;amp; Commercial Management (IACCM) - has &lt;a href="http://tcummins.wordpress.com/2009/07/07/the-state-of-automation/"&gt;written a post&lt;/a&gt; suggesting why market growth hasn't met those expectations.&lt;br /&gt;&lt;br /&gt;His reasons?&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Difficulty in fixing cross-functional processes; because contracting cuts across Legal, Finance, Sales, Procurement and Operations there is often a lack of executive sponsorship to fix the end-to-end business process.&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Resistance by internal IT (who are forever being promised the 'imminent' arrival of a Contract Management module by their ERP provider).&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Under-appreciation by companies of the impact of the contracting processes on financial performance, company reputation, and risk management.&lt;/li&gt;&lt;/ul&gt;So, how much is contracting really costing you?&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-7003746566979251742?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/9VBI9kb03t4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/7003746566979251742/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/07/tim-cummins-on-whats-holding-back.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/7003746566979251742?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/7003746566979251742?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/9VBI9kb03t4/tim-cummins-on-whats-holding-back.html" title="Tim Cummins on what's holding back  contract lifecycle automation" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/07/tim-cummins-on-whats-holding-back.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0IASHo4cCp7ImA9WxJVFUU.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-5908116675624614533</id><published>2009-07-02T10:00:00.004-04:00</published><updated>2009-07-02T20:39:09.438-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-02T20:39:09.438-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="word" /><category scheme="http://www.blogger.com/atom/ns#" term="formatting" /><category scheme="http://www.blogger.com/atom/ns#" term="documents" /><category scheme="http://www.blogger.com/atom/ns#" term="corrupt" /><category scheme="http://www.blogger.com/atom/ns#" term="drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="contracts" /><category scheme="http://www.blogger.com/atom/ns#" term="semi-standard" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="styles" /><title>How to cure the numbering headache in Word documents</title><content type="html">If you work with legal documents, you've probably had to contend with MS Word's &lt;a href="http://office.microsoft.com/en-au/word/HP051860441033.aspx"&gt;outline numbering&lt;/a&gt;. In which case you may have also suffered the pain of your numbering spontaneously going haywire.&lt;br /&gt;&lt;br /&gt;Sound familiar? Then read on.&lt;br /&gt;&lt;br /&gt;There are 3 ways to avoid spontaneous outline numbering corruption.&lt;br /&gt;&lt;ol&gt;&lt;li&gt;&lt;b&gt;The &lt;/b&gt;&lt;a href="http://en.wikipedia.org/wiki/IBM_Selectric_typewriter"&gt;&lt;b&gt;Typewriter&lt;/b&gt;&lt;/a&gt;&lt;b&gt; approach&lt;br /&gt;&lt;/b&gt;&lt;br /&gt;Best for single-page documents being drafted by Baby Boomers.&lt;br /&gt;(Examples: none that I can think of.)&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;b&gt;The &lt;/b&gt;&lt;a href="http://www.shaunakelly.com/word/numbering/OutlineNumbering.html"&gt;&lt;b&gt;Shauna Kelly&lt;/b&gt;&lt;/a&gt;&lt;b&gt; approach&lt;br /&gt;&lt;/b&gt;&lt;br /&gt;Best for long bespoke documents.&lt;br /&gt;(Examples: books, journal articles, instruction manuals.)&lt;br /&gt;&lt;br /&gt;&lt;/li&gt;&lt;li&gt;&lt;b&gt;The &lt;/b&gt;&lt;a href="http://www.exari.com/document-assembly.html"&gt;&lt;b&gt;Automated&lt;/b&gt;&lt;/a&gt;&lt;b&gt; approach&lt;br /&gt;&lt;/b&gt;&lt;br /&gt;Best for rule-driven, semi-standard contracts and other complex documents.&lt;br /&gt;(Examples: proposals; &lt;a href="http://www.exari.com/demo-trial.html"&gt;services agreements&lt;/a&gt;; renewal letters; employment packages.)&lt;/li&gt;&lt;/ol&gt;So, the next time you're about to start bashing away on the keyboard, make sure your outline numbering's up to the task.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-5908116675624614533?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/Tk66dKp0krA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/5908116675624614533/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/07/how-to-cure-numbering-headache-in-word.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5908116675624614533?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/5908116675624614533?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/Tk66dKp0krA/how-to-cure-numbering-headache-in-word.html" title="How to cure the numbering headache in Word documents" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/07/how-to-cure-numbering-headache-in-word.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkIAQn85fSp7ImA9WxJWE0Q.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-2243028481508247450</id><published>2009-06-19T01:46:00.013-04:00</published><updated>2009-06-19T02:55:43.125-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-19T02:55:43.125-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="strategy" /><category scheme="http://www.blogger.com/atom/ns#" term="technology" /><category scheme="http://www.blogger.com/atom/ns#" term="legal" /><category scheme="http://www.blogger.com/atom/ns#" term="lawyers" /><category scheme="http://www.blogger.com/atom/ns#" term="drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="innovation" /><category scheme="http://www.blogger.com/atom/ns#" term="law departments" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><category scheme="http://www.blogger.com/atom/ns#" term="law firms" /><title>Susskind: Rio Tinto deal heralds huge changes</title><content type="html">I just read &lt;a href="http://business.timesonline.co.uk/tol/business/law/article6523920.ece"&gt;Richard Susskind's take&lt;/a&gt; on Rio Tinto's &lt;a href="http://blog.exari.com/2009/06/rio-tinto-to-slash-legal-costs-by-20.html"&gt;legal process outsourcing&lt;/a&gt; (LPO) deal, which he describes as "ground-breaking."&lt;div&gt;&lt;/div&gt;&lt;blockquote&gt;&lt;div&gt;&lt;i&gt;Why is the arrangement with CPA [Rio's LPO partner] so significant? Primarily because it is evidence of a profound change in the legal world. In-house lawyers are under great pressure to reduce their head count and to spend less on external law firms, but, at the same time, their workload is increasing.&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;i&gt;&lt;br /&gt;&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;i&gt;Clients, in short, need their advisers to provide more-for-less.&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;/blockquote&gt;&lt;div&gt;As we have noted &lt;a href="http://blog.exari.com/2009/06/do-you-work-for-one-of-10-most.html"&gt;previously&lt;/a&gt;, "more-for-less" cannot be achieved by focusing purely on hourly rates. Susskind agrees and posits that offshoring will provide one of many alternative approaches, another being "&lt;i&gt;computerisation, using tools such as automatic document drafting and workflow technology.&lt;/i&gt;"&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;The takeaway&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Rio Tinto has made it clear that it &lt;a href="http://www.adamsmithesq.com/archives/2008/06/gcs_may_be_complaining_bu.html"&gt;really does want change&lt;/a&gt;. Whether you're in-house or in a law firm, you've got to decide whether this is a one-off or the start of a trend.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;If it's the latter, you better work out what it means for you and how you're going to respond.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-2243028481508247450?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/sSU-zUACK4A" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/2243028481508247450/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/06/susskind-rio-tinto-deal-heralds-huge.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2243028481508247450?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2243028481508247450?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/sSU-zUACK4A/susskind-rio-tinto-deal-heralds-huge.html" title="Susskind: Rio Tinto deal heralds huge changes" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/06/susskind-rio-tinto-deal-heralds-huge.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04FQnkzcCp7ImA9WxJWE0U.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-6885389101169530302</id><published>2009-06-18T22:27:00.018-04:00</published><updated>2009-06-19T01:38:33.788-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-19T01:38:33.788-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="london" /><category scheme="http://www.blogger.com/atom/ns#" term="processes" /><category scheme="http://www.blogger.com/atom/ns#" term="legal" /><category scheme="http://www.blogger.com/atom/ns#" term="lawyers" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="innovation" /><category scheme="http://www.blogger.com/atom/ns#" term="law departments" /><title>Rio Tinto to slash legal costs by 20%</title><content type="html">In an effort to reduce it's annual legal bill by 20% (or around US$20M), Rio Tinto is &lt;a href="http://business.timesonline.co.uk/tol/business/industry_sectors/natural_resources/article6524531.ece"&gt;outsourcing legal work&lt;/a&gt; to India. According to The Times, the work will include "tasks such as reviewing documents and drafting contracts."&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Targeting expensive lawyers&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Rio estimates that its Indian operation "will be seven times cheaper than comparable lawyers in London." Rio's legal process outsourcing partner, &lt;a href="http://www.cpaglobal.com/media_centre/press_releases/0145/rio_tinto_signs_legal_services"&gt;CPA Global&lt;/a&gt;, "provided us with fresh thinking about how to unlock real savings on our legal costs without altering the level of service we offered our internal clients," said Leah Cooper, Rio’s managing attorney.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The test will be whether Rio can actually maintain current service levels after transferring their processes to India.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Other benefits&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;"As more of our standard legal work is filtered though to CPA Global, we will have more time to lift our heads up from the day-to-day reactive delivery of legal services and focus on being more proactive," said Cooper.&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Where to next?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;If the offshoring really enables Rio's lawyers to focus on being more proactive, it could open up other opportunities. For example, it may just give Rio's lawyers the bandwidth they need to look at improving service delivery, rather than simply maintaining it.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Now, as we've previously noted, the only way to do that without increasing costs is &lt;a href="http://blog.exari.com/2009/06/do-you-work-for-one-of-10-most.html"&gt;through innovation&lt;/a&gt;. And increasing productivity by transforming and automating your business processes is not easy. It takes a big commitment of time and effort from subject matter experts and other skilled employees.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;However, the good news is that success results in valuable competitive advantage that's difficult to replicate. Which means that, at the very least, you owe it to your clients and shareholders to investigate the business case for taking service delivery to the next level.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;So, what are you waiting for?&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-6885389101169530302?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/8mC4R3vOR4Q" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/6885389101169530302/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/06/rio-tinto-to-slash-legal-costs-by-20.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/6885389101169530302?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/6885389101169530302?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/8mC4R3vOR4Q/rio-tinto-to-slash-legal-costs-by-20.html" title="Rio Tinto to slash legal costs by 20%" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/06/rio-tinto-to-slash-legal-costs-by-20.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C08FQ3w5eip7ImA9WxJWE0Q.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-3345494583234576438</id><published>2009-06-12T02:35:00.032-04:00</published><updated>2009-06-19T02:10:12.222-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-19T02:10:12.222-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="processes" /><category scheme="http://www.blogger.com/atom/ns#" term="legal" /><category scheme="http://www.blogger.com/atom/ns#" term="drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="automation" /><category scheme="http://www.blogger.com/atom/ns#" term="innovation" /><category scheme="http://www.blogger.com/atom/ns#" term="law departments" /><title>The 10 Most Innovative Legal Departments</title><content type="html">&lt;div&gt;Is your department innovative? This is the question being asked by &lt;a href="http://www.insidecounsel.com/Pages/TheIC-10.aspx"&gt;Inside Counsel&lt;/a&gt;, a magazine for in-house legal departments.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;Why is innovation important?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;The answer, in a nutshell, is that innovation is what enables organisations to remain competitive.  It's transformational in nature, enabling step changes in productivity (as opposed to incremental improvements). It's what drives progress. And in corporations, innovation is just as important in the legal function as in sales, procurement or HR.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;What is not innovation?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Many in-house lawyers are under the misconception that beating their external law firms over the head about hourly rates constitutes innovation. (Funnily enough, one of last year's submissions was a "patent-pending method for forcing law firms to lower their rates.") Another common approach is to shift work from top tier providers to chepear firms or regional offices.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Focusing on billing rates and cost cutting isn't innovation.  All it does is lead to bill padding, poor service or both.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;So what is innovation?&lt;/b&gt;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Real innovation involves finding new ways of doing things.  And sustainable innovation can only be achieved by revamping and automating key business processes.  What are the major activities and processes in your legal department? Is contract drafting/review/negotiation up there? If so, how effective is your current process? Have you ever analysed it? Could it be made cheaper, faster or less risky?&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;If your contracting process is world's best practice, &lt;a href="http://www.surveymonkey.com/s.aspx?sm=QTU02hrWZDhoJDkiP1oCPA_3d_3d"&gt;nominate&lt;/a&gt; for the &lt;b&gt;Inside Counsel 10&lt;/b&gt; now. If not, &lt;a href="http://www.exari.com/demo-trial.html"&gt;test drive Exari&lt;/a&gt; to see what's possible.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-3345494583234576438?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/xBVxjePvJ-I" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/3345494583234576438/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/06/do-you-work-for-one-of-10-most.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/3345494583234576438?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/3345494583234576438?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/xBVxjePvJ-I/do-you-work-for-one-of-10-most.html" title="The 10 Most Innovative Legal Departments" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/06/do-you-work-for-one-of-10-most.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUMEQH05cCp7ImA9WxJWEUQ.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-3636484122386315937</id><published>2009-06-09T11:00:00.033-04:00</published><updated>2009-06-16T20:10:01.328-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-16T20:10:01.328-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="formatting" /><category scheme="http://www.blogger.com/atom/ns#" term="legal" /><category scheme="http://www.blogger.com/atom/ns#" term="lawyers" /><category scheme="http://www.blogger.com/atom/ns#" term="drafting" /><category scheme="http://www.blogger.com/atom/ns#" term="contracts" /><category scheme="http://www.blogger.com/atom/ns#" term="contract" /><category scheme="http://www.blogger.com/atom/ns#" term="document" /><category scheme="http://www.blogger.com/atom/ns#" term="agreement" /><title>Drafting contracts to be understood</title><content type="html">&lt;span class="Apple-style-span"&gt;&lt;div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"&gt;&lt;span class="Apple-style-span"  style="font-family:georgia;"&gt;Everyone who deals with legal documents can point to unintelligible agreements. Many would argue that this is the aim of the drafter.&lt;/span&gt; &lt;/div&gt;&lt;br /&gt;&lt;div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"&gt;&lt;span class="Apple-style-span"&gt;&lt;span style="font-family:georgia;"&gt;That may sometimes be the case. But, more often, the drafter(s) in question simply know no better. Most lawyers are NEVER taught how (or why) to draft in &lt;/span&gt;&lt;a href="http://en.wikipedia.org/wiki/Plain_English"&gt;&lt;span style="font-family:georgia;"&gt;Plain English&lt;/span&gt;&lt;/a&gt;&lt;span style="font-family:georgia;"&gt;.&lt;/span&gt;&lt;/span&gt; &lt;/div&gt;&lt;br /&gt;&lt;div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"&gt;&lt;span class="Apple-style-span"  style="font-family:georgia;"&gt;If you're interested in removing ambiguity and communicating more clearly, there are a couple of sites you should check out.&lt;/span&gt;&lt;/div&gt;&lt;div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"&gt;&lt;ul&gt;&lt;li&gt;&lt;span class="Apple-style-span"&gt;&lt;a href="http://adamsdrafting.com/"&gt;&lt;span style="font-family:georgia;"&gt;Adams Drafting&lt;/span&gt;&lt;/a&gt;&lt;span style="font-family:georgia;"&gt; assesses all manner of contract language and advises on best practices for clear and concise usage. &lt;/span&gt;&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;ul&gt;&lt;li&gt;&lt;span class="Apple-style-span"&gt;&lt;a href="http://www.typographyforlawyers.com/"&gt;&lt;span style="font-family:georgia;"&gt;Typography for Lawyers&lt;/span&gt;&lt;/a&gt;&lt;span style="font-family:georgia;"&gt; focuses, not on the words per-se, but on their visual presentation. This site explains how poor text layout impedes readability and comprehension and tips for better typography.&lt;/span&gt;&lt;/span&gt;&lt;span style="font-family:georgia;"&gt; &lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"&gt;&lt;span class="Apple-style-span"&gt;&lt;span style="font-family:georgia;"&gt;And for an interesting take on the proliferation of legal gobbledygook in contracts, see &lt;/span&gt;&lt;a href="http://www.providedhowever.com/blog/2009/05/why-our-agreements-look-like-crap/"&gt;&lt;span style="font-family:georgia;"&gt;Why Our Agreements Look Like Crap&lt;/span&gt;&lt;/a&gt;&lt;span style="font-family:georgia;"&gt;.&lt;/span&gt;&lt;/span&gt;&lt;span style="font-family:georgia;"&gt; &lt;/span&gt;&lt;/div&gt;&lt;br /&gt;&lt;div style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px"&gt;&lt;span style="font-family:georgia;"&gt;Automated &lt;a href="http://www.exari.com/document-assembly.html"&gt;document assembly&lt;/a&gt; software can help keep your contracts consistent and compliant, but the document author still must use clear, understandable language.&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-3636484122386315937?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/j99DizsfNzg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/3636484122386315937/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/06/drafting-contracts-to-be-understood.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/3636484122386315937?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/3636484122386315937?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/j99DizsfNzg/drafting-contracts-to-be-understood.html" title="Drafting contracts to be understood" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/06/drafting-contracts-to-be-understood.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkcMQnk-eyp7ImA9WxJXEkw.&quot;"><id>tag:blogger.com,1999:blog-587696811840434233.post-2811271640990577586</id><published>2009-06-05T10:54:00.011-04:00</published><updated>2009-06-05T11:01:23.753-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-05T11:01:23.753-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Document Assembly" /><category scheme="http://www.blogger.com/atom/ns#" term="banking" /><category scheme="http://www.blogger.com/atom/ns#" term="document automation" /><title>How to Fix Turnaround Times</title><content type="html">The previous post ended by asking how banks could &lt;a href="http://blog.exari.com/2009/06/australias-big-4-banks-big-mortgage_04.html"&gt;better handle unanticipated spikes&lt;/a&gt; in lending applications. Or more generically, how can a service provider respond effectively to an increase in client requests?&lt;br /&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;Scalability&lt;/span&gt;&lt;br /&gt;And that doesn't mean hiring more people. It means automating processes to capture quality data up-front and remove bottlenecks to downstream fulfillment. The real issue is how to do that properly. Tactical solutions focussed on an individual function or channel cause as many problems as they solve, while strategic solutions are out-of-date before they're implemented.&lt;br /&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;Quick wins&lt;/span&gt;&lt;br /&gt;The key is to start with a quick win. Rapid deployment to handle a targeted problem. Then, after solving that problem (and celebrating the "win"), iterate.&lt;br /&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;The right tool for the job&lt;/span&gt;&lt;br /&gt;But to do this effectively you need the right platform. From the start, the system needs to be:&lt;br /&gt;&lt;li&gt;Robust - to mimize expensive down-time.&lt;br /&gt;&lt;li&gt;Scalable - to reliably handle increased volumes.&lt;br /&gt;&lt;li&gt;Flexible - able to handle new business situations.&lt;br /&gt;&lt;li&gt;Usable - to be embraced by the business. &lt;/li&gt;&lt;br /&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;It's all about the user&lt;/span&gt;&lt;br /&gt;It's the last requirement - usability - that is most often overlooked. And, it's the most important. If a system is not designed for business users - as opposed to by IT - it will fail. For a system to be owned by business users, it needs to be easy to use so the business can maintain it without needing to continually go back to IT.&lt;br /&gt;&lt;br /&gt;&lt;span class="Apple-style-span" style="FONT-WEIGHT: bold"&gt;The result&lt;/span&gt;&lt;br /&gt;By automating their document intensive processes with document assembly software, Exari's clients have been able to cut cycle times and costs by 70%. Think about how much more productive you could be. You'd be amazed how much you can achieve when the business "owns" the solution to its problems. &lt;a href="http://www.exari.com/forms/contact-us.html"&gt;Contact us&lt;/a&gt; to learn the ROI for your project.&lt;div class="blogger-post-footer"&gt;The Exari Blog&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/587696811840434233-2811271640990577586?l=blog.exari.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TheEngineRoom/~4/Yu8ethEHdMY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://blog.exari.com/feeds/2811271640990577586/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://blog.exari.com/2009/06/how-to-fix-turnaround-times.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2811271640990577586?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/587696811840434233/posts/default/2811271640990577586?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheEngineRoom/~3/Yu8ethEHdMY/how-to-fix-turnaround-times.html" title="How to Fix Turnaround Times" /><author><name>Andrew Davis</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="05382984969493536100" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://blog.exari.com/2009/06/how-to-fix-turnaround-times.html</feedburner:origLink></entry></feed>
