Microsoft Office 2013 or 2010 for business?

For years I've been using Office 2010 and it's just fine. Recently we put 2013 on a few new PC's, and I'm wondering if we should roll it out across the board or even continue putting it on new PC's, or stick with 2010.

99% of our users don't need any of the new features in 2013 as they barely use the features in 2010.

What I like about 2013:
The look and feel is a bit nicer
Outlook Cached Mode can be set to only cache recent emails, reducing the OST file size.

What I Don't like about 2013:
"Save" adds an extra step for me to pick "save to a directory, not sky drive"
Outlook contact cards is very annoying and seems buggy
Overall feels slower than 2010, especially on VDI's... but I can't put my finger on that.
Outlook seems a bit buggy (certain users reporting random strange issues)

Wondering what everyone else is doing on this. Is Office 2013 kind of like WIndows 8, where most businesses are skipping it and staying with 7? I don't want to do it just because it's the newest product, I would rather stick with what is rock solid. We don't need any skydrive/365 integration right now. Most users just need Word, Excel, and Outlook.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Richard DanekeTrainerCommented:
Since the files are compatible, I don't think the issue is compelling.  

I do like 2013 for making the less used features easier to use.  

Using the folder list (and pinning your important folders) can be helpful in reminding users where they have saved the file.

I, also, think users need to learn to be flexible in the operation of the programs.  Changes will continue.  Office 2015 and Windows 10 is around the corner.  

If we are to set a value for our expertise, shouldn't it be in helping people live with the changes or should it be in helping people avoid the changes?
I "upgraded" from Office 2010 32bit to Office 365 (Office 2013) 64 bit.
I had a lot of vba code in Excel, some of it dating back to 1998 and before. I have been programming spreadsheets since VisiCalc and MultiPlan days.

For me, anyway, Excel 2013 has an extremely low fault tolerance (it crashes on things which were not a problem back in the day) and in true Microsoft form most of the time Excel did not tell me why it crashed and the rest of the time it lied about why it crashed.

After 4 months of extensive debugging and logic rethinking, I have been running for 7 days without a crash.

To Excel's credit, it did a fair job of recovering corrupted workbooks. On the other hand, Excel corrupted the workbooks when it crashed. Biggest problem I face with recovered workbooks was Excel tended to "fix" them by removing ALL named ranges and conditional formats.

I agree with Richard, as experts, we should be focusing on dealing with the changes. Some years ago, I got "smart" and skipped a few generations in hardware and operating systems. Then my computers decided to die and guess what - their replacements did not come with the old systems and a lot of the original software would not install on the new stuff.
The bottom line - I now run the "latest" and "greatest" in hardware and software. I also spend a lot of time on forums such as this looking for tips and tricks to tweak (or work-around) the new and improved offerings from Microsoft (and others).

Live long and prosper.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tabushAuthor Commented:
Thanks Guys!
Richard DanekeTrainerCommented:
Thank you.  I did neglect to emphasize to ONLY USE the 32-bit Office.  Regardless of the operation system being 32- or 64- bit, the Office installed should be 32-bit.   There have been compatibility issues as mentioned by Jim when installing the 64-bit versions.
I tend to agree with Richard about using the 32-bit Office as long as you don't need the additional memory supposedly available to the 64 bit version.
While I was tracking down my problems, Excel, and all the "expert" advice I found on many forums, led me to believe I needed the extra memory capacity of 64 bit.
I cannot confirm if memory was part of my problem.
However, I was able to resolve, so far, the compatibility issues of 32-bit vs 64 bit for Excel which is the only part of office I code with VBA. I do use Excel VBA to send invoices from my billing program via email through Outlook and have had no problems with the code which was developed in Office 2010, 32 bit.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.