Update Visual Basic for Applications
Visual Basic for Applications is still version 7.1 from 2012. It's high time that power user portion of the application received updates to the interface, IntelliSense, and features. That portion of the program needs to be aligned with the current features now available within the Microsoft Suite. It also needs a facelift to the Userforms palette. I suggest starting with Excel, where VBA is most widely used, then PowerPoint, Word, Outlook.
Don't go destroying developer's programs, just add interoperability, functions, and facelift.
James Lee commented
Comment on an idea about VBA IDE that's under review at https://officespdev.uservoice.com/forums/224641-feature-requests-and-feedback/suggestions/15446658-give-the-vba-ide-a-major-overhaul-finally
Ted Power User commented
If Microsoft does not continue to keep Visual Basic in excel, then Office Excel is worthless. They have absolutely no idea how people use it, because the managers at Microsoft have not actually used it in real work businesses. EVERYONE uses VB to help with data extracts and repetitive manipulation. They need to hire real world power users that used extensive data manipulation and stop hand picking analysts that can model using office the way they think people should use it. That would be unprofessional and is not addressing how people actually NEED to use it.
Unfortunately MS is no longer actively developing VBA. It is as far along as it will ever get. The Excel libraries will probably be updated as new features are added to Excel, but I don't expect to see any further enhancements to the VBA IDE itself. Fortunately, MS has no plans to discontinue VBA either. There are too many millions of lines of customer VBA code written for MS to just kill it. Killing VBA would probably be the death of Excel. Here's a short little writeup written by a MS Excel MVP that explains the future of VBA.
On a positive note, I have also read that MS is planning on replacing VBA with something a little more robust. Perhaps, and this is just a wish list item for me, MS will integrate VBA like development into Visual Studio, which is capable of supporting many different languages, including 3rd party languages. Just imagine the possibilities if you could pick the language you wanted to write your macro in.
I'm keeping my fingers crossed for a more robust environment than VBA provides.