Call 855-808-4530 or email [email protected] to receive your discount on a new subscription.
“Must-have” software, hardware and training seems to come in waves. In my 25 years working with personal computers, I've seen peaks and valleys in upgrades. In the late 1980s and early '90s, moving to personal computers, networks, databases, spreadsheets and from DOS to Windows was at its peak. Later on, Microsoft Word 97 was at the top, as were PDAs, document management systems, Office 2003, Windows 7 and wireless. The valleys can be comfortable once the kinks are ironed out and the training has been completed. I believe, relatively speaking that is, that we've been in a valley lately. But not anymore.
We're on a peak again, a rather high one at that. With Office 2010 (32 and 64 bit), along with all of the third-party (major and minor) applications that are trying to keep up, I'm feeling the air get a bit thinner.
Let's talk about those kinks, how to minimize them, and spend more time in the comfort zone where the air is easier to breathe.
The Initial Decision to Upgrade
If you were on that rather mid-sized peak of Vista/Windows 7 and Office 2007, you may be just fine (although this column is not intended to advise on whether or not to upgrade). Your Office version is capable of both backward and forward document compatibility. The document management systems are reasonably stable, and you've probably dealt with the template/macro issues by now. You may lose a few features from 2010 files when opening them in 2007, but most legal documents don't use all of the new bells and whistles that Word provides with each new release anyway.
Thinking About a Hybrid Environment?
Some firms are mixing and matching Office versions in their environment (for example, Word, Excel and PowerPoint 2003 with Outlook 2010), or running full installs of both Office 2003 and Office 2010 on the machine (side-by-side). With either of these, it is critical that you work with your third-party vendors, integrators, and even your Microsoft tech in some instances, to be sure that: 1) the mission-critical third-party software will run in that environment; 2) the integrator knows exactly what they're doing as far as where to install which component, how the registry will be affected and how to deploy; 3) if the current workflow your users are familiar with will be impacted; and 4) you've got all of the necessary hardware/system resources.
If you do plan on running a hybrid setup, lay out a timeline for a full deployment in the not-too-distant future of just one version of Office. If you depend on this type of environment being long-term, you will surely run up against some of the issues listed above.
What Do I (or My Integrator) Need to Know Moving Forward?
Once the decision has been made to upgrade, and after you've talked to your third-party vendors, integrators, etc., the following are some tried and true tips.
What Next?
Prior to a full deployment to your firm, you'll need to run a few machines in a test environment to ensure that there are no conflicts. If you don't have a separate test environment, try to set aside a machine or two, and designate a user(s) who doesn't have a heavy production load and can “put it through its paces.” The person you designate will ideally have an open-mind, and understand her role. Certain people will poison the waters for the rest of the staff if they run across an issue and don't/won't realize she is “testing” and that things will get resolved based on her feedback. Run these tests as both a standard user and administrator.
Many large firms create a Pilot Group. This may be a practice group, power users or Word Processors. When you have as much feedback as you would from a group that is working “live” with the new configuration, you'll be better prepared prior to deploying firm wide. The bottom line is that you should endeavor to create plenty of good documentation for your IT staff and trainers during the entire process.
Conclusion
Hopefully this column provides food for thought before moving forward with a big change. Spend the time getting intimate with your new configuration prior to deployment. The air won't be so thin once you get over that peak.
“Must-have” software, hardware and training seems to come in waves. In my 25 years working with personal computers, I've seen peaks and valleys in upgrades. In the late 1980s and early '90s, moving to personal computers, networks, databases, spreadsheets and from DOS to Windows was at its peak. Later on,
We're on a peak again, a rather high one at that. With Office 2010 (32 and 64 bit), along with all of the third-party (major and minor) applications that are trying to keep up, I'm feeling the air get a bit thinner.
Let's talk about those kinks, how to minimize them, and spend more time in the comfort zone where the air is easier to breathe.
The Initial Decision to Upgrade
If you were on that rather mid-sized peak of Vista/Windows 7 and Office 2007, you may be just fine (although this column is not intended to advise on whether or not to upgrade). Your Office version is capable of both backward and forward document compatibility. The document management systems are reasonably stable, and you've probably dealt with the template/macro issues by now. You may lose a few features from 2010 files when opening them in 2007, but most legal documents don't use all of the new bells and whistles that Word provides with each new release anyway.
Thinking About a Hybrid Environment?
Some firms are mixing and matching Office versions in their environment (for example, Word, Excel and PowerPoint 2003 with Outlook 2010), or running full installs of both Office 2003 and Office 2010 on the machine (side-by-side). With either of these, it is critical that you work with your third-party vendors, integrators, and even your
If you do plan on running a hybrid setup, lay out a timeline for a full deployment in the not-too-distant future of just one version of Office. If you depend on this type of environment being long-term, you will surely run up against some of the issues listed above.
What Do I (or My Integrator) Need to Know Moving Forward?
Once the decision has been made to upgrade, and after you've talked to your third-party vendors, integrators, etc., the following are some tried and true tips.
What Next?
Prior to a full deployment to your firm, you'll need to run a few machines in a test environment to ensure that there are no conflicts. If you don't have a separate test environment, try to set aside a machine or two, and designate a user(s) who doesn't have a heavy production load and can “put it through its paces.” The person you designate will ideally have an open-mind, and understand her role. Certain people will poison the waters for the rest of the staff if they run across an issue and don't/won't realize she is “testing” and that things will get resolved based on her feedback. Run these tests as both a standard user and administrator.
Many large firms create a Pilot Group. This may be a practice group, power users or Word Processors. When you have as much feedback as you would from a group that is working “live” with the new configuration, you'll be better prepared prior to deploying firm wide. The bottom line is that you should endeavor to create plenty of good documentation for your IT staff and trainers during the entire process.
Conclusion
Hopefully this column provides food for thought before moving forward with a big change. Spend the time getting intimate with your new configuration prior to deployment. The air won't be so thin once you get over that peak.
End of year collections are crucial for law firms because they allow them to maximize their revenue for the year, impacting profitability, partner distributions and bonus calculations by ensuring outstanding invoices are paid before the year closes, which is especially important for meeting financial targets and managing cash flow throughout the firm.
Law firms and companies in the professional services space must recognize that clients are conducting extensive online research before making contact. Prospective buyers are no longer waiting for meetings with partners or business development professionals to understand the firm's offerings. Instead, they are seeking out information on their own, and they want to do it quickly and efficiently.
Through a balanced approach that combines incentives with accountability, firms can navigate the complexities of returning to the office while maintaining productivity and morale.
The paradigm of legal administrative support within law firms has undergone a remarkable transformation over the last decade. But this begs the question: are the changes to administrative support successful, and do law firms feel they are sufficiently prepared to meet future business needs?
Counsel should include in its analysis of a case the taxability of the anticipated and sought after damages as the tax effect could be substantial.