We did announce it before we installed the update: on the forums. Announcements ingame are made once the update is there, to avoid confusion.
As a PMP certified Project Manager, communication is everything. We are trained to over communicate. Literally use as many methods as often as possible to get the message across. One mentor taught me to continue communicating until I hear the target audience scream "Stop, we get it!"
Different folks receive information differently. This is especially true in this game. There are sooo many tools to do this (Forums, in game pop ups, opening billboard messaging, circular messages, chat, direct e-mail (as has been used for diamonds, etc.). And I am sure I missed a few. You know this Inno. As has been pointed out many times, only a fraction of players use the Forums (shame on non-users for neglecting this resource). Shame on YOU Inno for not doing your part to make sure every player knew about this weeks in advance, to be able to prepare (if not longer). Shame on YOU Inno for not doing the work to calculate the impact on every structure for every level AND publish this via YOUR tools (you had this information somewhere, you had to have it to make the change, right?). I had to get this information on a 3rd party site (Elvenarchitect). Shame on YOU Inno for seemingly not planning this impact (or simply not caring) to hit at a less critical time. There are TWO events going on ATM. And again (similar to the Bell Spire / Lighthouse "re-balancing"), shame on YOU Inno for taking something away after the fact rather than planning from the beginning.
It is ALL about communication and planing. I get that the world is a changing environment. I get that this is an evolving game. I get that this is ONLY a game. But REALLY??? You couldn't make the effort to make sure such a drastic change wouldn't be a surprise to so many players???
As an Archmage, I have been doing my best (to keep my crew motivated, to explain what I find in the Forums, to help guide as I can, and to defend as devils-advocate when possible). But, I just can't back you up on the methods used for this implementation. I am just sad at this point.