Interesting study. Obtained from Ruckus, but seems like a legit testing system.
Syracuse University recently completed comprehensive testing of ‘top-of-the-line’ 802.11n AP’s. This testing included Cisco 3602i, Aruba AP135, AeroHive AP330, Meraki MR24 and Ruckus ZF7982. Ruckus won this bake-off.
It is not a secret that when you breakdown larger complex change into smaller components in a simple way, you can get deeper understanding of the whys and hows. The idea of using a “Page Per Change” document is basically that you, being the project manager, take the issues and make them as direct as possible and illustrate the before and after on the same page. If you are able to do this, you provide a few benefits for your audience;
Brief explanations of each issue they can reference when talking with you. You will get more informed feedback.
Give people the ability to see you have done your homework and have built an understanding of the changes involved.
Allow people to be charitable. Odds are they will at least find a few pages they can empathize and agree with even if they are reluctant to swallow all the upcoming changes.
Provide a document everyone can reference easily when discussing issues among their own groups or departments.
Allows you to clarify and define “feedback” instead of getting unfiltered complaints.
Remove excuses for people to not be fully aware of the changes. Images and single pages are not too much to have to take on as a user if there is real concern.
Attached is a document I used last year around this time to summarize a website transition. We were redesigning the site and making some changes that affected thousands of users. The project was titled “Website Fixes” because the project with WhippleHill was meant mostly to address and correct issues in our original design of the website after using it for a few years. Click the image below to get a copy of the document to give you some ideas if you think the “Page Per Change” might work for your constituency. This document is for a website redesign, but the idea might work with any type of transition.
In my experience, when you are able to generate a document like this, it helps you and the audience affected because it helps get people on the same page while allowing you and your team to get the word out to others in an easy to digest method.
Hope this idea might be of help to you.
Note: The final document had a few other pages before going to the “Page Per Change” model.But, I used the same “single page” mindset for: a cover, a timeline, a summary of the project, page with website links on how to provide constructive feedback and contact information.