The Web Content Administrator at the Wayne State University School of Business Administration is responsible for creating, editing and formatting textual and graphical content for the School of Business Administration website. The Web Content Administrator assists with the general management of the website and works with important stakeholders including Wayne State University’s centralized Marketing/Web and Development teams, business school faculty, staff, students and alumni.
Primary responsibilities include
- Researching, planning and writing fresh content for the website. This may include:
- Coordinating photography and graphics
- Coordinating and conducting interviews
- Participating in meetings
- Evaluating content and recommending best practices
- Entering content into the University’s custom Content Management System and formatting it
- Developing online event promotions and monitoring promotion schedules
- Assisting with creating a planned review system to ensure content and links remain current
- Other duties as needed
Minimum qualifications
- Outstanding communication skills, especially written
- Prior Web writing experience and a keen understanding of writing for the Web versus other media
- Experience working with a Web content management system or similar Web-based system (i.e. blog)
- Basic knowledge of HTML
- Some graphic design and photo editing ability (basic working knowledge of Adobe Photoshop)
- Basic knowledge of social media websites (YouTube, Flickr, Facebook, Twitter, etc.)
Schedule: 20 hours per week
Work is performed on-site at Wayne State’s Detroit campus on a predetermined schedule. Schedule is flexible, but must be designed so hours are worked during WSU’s normal business hours: between 8:30 am and 5 pm, Monday – Friday.
Salary: Up to $19 per hour, depending on experience. This position does not provide fringe benefits.
Application:
This position is part of the School of Business Administration Marketing & Communications department and reports to the Director of Marketing & Communications.
Please send a cover letter, resume, and at least 2 Web writing samples by February 17, 2012 to:
Jenny Powell-Grosvenor or fax 313-577-4557.
Last year I was fortunate enough to attend two conferences. The first, Internet User Experience (IUE), was in October on the campus of Washtenaw Community College in Ann Arbor, Mich. The other, Usability Week through Nielsen Norman group (NN/g), was in December in Las Vegas. Both conferences had caliber in the information presented.
Internet User Experience (IUE)
At IUE, I was introduced to the Agile work environment. This environment was based on an Agile Software Development methodology where projects are broken into smaller and shorter deliverable phases with the initial product meeting the core needs of the client. I attended sessions such as Connecting with Customers: User Generated Content, Mosh Pit Memoirs: Lessons and Insights on Creative Collaboration, The Top 10 Things Every Designer Needs to Know About People, and Better User Requirements Through Story Mapping. My ultimate favorite session, though, was Hold the Sprinkles! Cupcake, Layers and Agile UX Design.
This session summarized the Agile method but applied it to design. The presentation was creative and very thought-out as Carissa Demetris created the parallelism in the process of designing to making a cupcake. Every project has base requirements just like a cupcake has cake as its base. The next layer in a project use enhancements like a cupcake uses frosting, followed by embellishments which would be the sprinkles. How does this approach apply in real projects? An example would be designing a basic login page – our cupcake. The frosting/enhancement for this project would be adding a radio button to remember the user or having a “Forgot password” link. The sprinkles/embellishment would be adding a Facebook login area. Carissa mentioned that most of the time, the need for “sprinkles” comes from the business owners, marketing dept. or someone other than the user. For the most part, these are wish-list items of the higher-ups who project their perception of what their users need. These embellishments don’t add to user experience or the goal, however.
In an Agile environment, the first iteration would be developing the login. If the budget and time hasn’t run out, there’s an opportunity to add the enhancement feature to either remember the user or have a “Forgot password” link. We now have our first iteration that meets our client’s core needs/goals while staying on budget and time. From experience, some of the projects I work on where “sprinkles” are elevated much higher than what they should be, cause delay, add more work and return little value. Carissa concluded with the mantra, “Embrace the cake, frost with care (to add the user experience), and hold the sprinkles.”
Nielson Norman group (NN/g) Usability Week
The NN/g in Vegas was a bit different from a handful of mini-sessions throughout the day like at most conferences. There, one session went for the entire day. The topics covered by the NN/g’s Usability Week ranged from writing for the Web, application design, Web usability guidelines, information architecture principles, mobile Web, and understanding how the human mind works when using the Web. I was blessed enough to have attended two days out of the seven. My goals coming into the conference were to understand our campus community’s thought processes and behavior and to know what tools to use to harvest data to build better websites. Based on that, the sessions I attended were “Web Design Lessons from Social Psychology” presented by John Boyd and “Research Beyond User Testing” presented by Christian Rohrer. I fully enjoyed both sessions but learning to understand behaviors and finding out how they can be manipulated made the Social Psychology session a personal favorite.
Dr. Boyd’s session was almost like a Social Psychology 101 course that talked about research and lab findings. I was amazed at how these findings are relevant on the Web today. Some really cool research was about learning, decision making and personal expectations.
Lets take “Learned Helplessness” which is when a person feels powerless due to constant failure and withdraws effort. When applied to websites, users start believing the effort they put in is useless, especially when trying to navigate a busy site or one that is too difficult to navigate through. The user’s multiple failed attempt to figure out the site will transmit as feelings of powerlessness and they eventually stop trying. This is when we see visitors leave a Web page and possibly never come back. However, if the user does figure out a way to navigate through a busy and difficult site in an unconventional way, the user has or will develop a “superstitious” behavior. This is when the user thinks if she clicks here, then there, then it will eventually work. As Web designers, we don’t want users to develop superstition or the feeling of helplessness. Knowing that these kinds of behaviors are real, website designs should have appropriate signals, architecture and organization in place per site.
Another cool study was on choice. The truth is, there is such a thing as too many choices. Users do not like being in a situation where there’s multiple options and vary minutely or are difficult to distinguish. Most users tend to walk away while some sophisticated choosers are willing to take the time to think about the choices. How does this apply on the Web? Perhaps on a shopping website featuring a slew of products under multiple categories right on the homepage. The sophisticated chooser will more likely check out the multiple categories while most people will leave the site. This behavior is best illustrated in the Jam Test done by Sheena Iyengar and Mark Lepper (see video below).
With so much information, I’m itching to put all of this knowledge to work! I can’t say enough how eternally grateful I am for the opportunities I have to grow professionally.
Some future conferences I have my eye on are:
- Human Factors International
- Nielsen Norman Group (NN/g) Usability Week 2012
- An Event Apart
- UI Seventeen
- Future of Web Design
A little extra:
Here’s a video from HFI that mentions Sheena I & Lepper’s Jam Study.
We’re always on the hunt to find ways to connect more people to the great things happening on Wayne State’s campus. If you have been following this blog you know these initiatives are often thought of and executed completely by us.
Chrome app
Not everyone has, or wants to have, the Today@Wayne website set as their homepage, and that is completely understandable. But we wanted to make sure it is as easy as possible for people to get to it. What better way than to have a Chrome app that is displayed every time the user opens a new tab or window? This way they can visit the daily newsletter at their leisure without having it load automatically every single time.
If you are a Google Chrome user you know the power of the extensions and apps. Both are lightweight and don’t slow down the browser like Firefox.
Google Chrome has gotten a little bit of flack because a vast majority of their “apps” are simply redirects to websites. In our case we’re currently doing just that. This approach isn’t our long term goal but it will get us started.
Looking forward
Chrome has an amazing ability to render HTML5 and take advantage of every bit of the users processing power. You can see that clearly with the popular Angry Birds app. Over the next few weeks and months we will be expanding the functionality of our app to take advantage of the user’s environment. Extending the website to use local storage and media queries to take full advantage of the users screen size and offline processing.
Download the Chrome app at: http://go.wayne.edu/today-chrome
The Wayne State football team had an amazing, record-breaking season this year. It was the first time our team it made the playoffs in the program’s 94-year history! These boys were hungry and they proved this by making it all the way to national championship.
It sadly ended when Pittsburg State (Kan.) beat us in the Division II national championship. Regardless of the loss, it put our team on the map.
I help monitor the social media for Wayne State and I was overwhelmed by the amount of support that flooded in over the last few months. Of course there was a lot of support from our student body but I was impressed by all the tweets from alums or ex-employees.
A lot of the time I help students with various issues, field complaints. With the football team’s recent success, however, I saw nothing but positive and encouraging tweets. There were many mentions of #warriorpride and it make me proud to be part of this community.
Tweets during the game
Below is a Wordle of the tweets that were sent during the game. This includes both WSU and Pitt State mentions. As you can see, Warrior pride dominated the twitter mentions.

Insight in to the tweets
Below is a graph of tweets that mentioned Wayne State football. We know that Twitter is a great source for trending events and we’re pleasantly surprised to see so many real time tweets about the games. As you can see below, as we moved through the championship games our mentions skyrocketed. At one point we had three different trending phrases in Detroit.

Some statistics
- 1,800+ football related tweets on championship game day
- 900+ people liked or commented on our game day Facebook status
- 18,000+ person reach for our game day Facebook status updates
- 15,000+ click-throughs on all football related tweets
- 325 new Twitter followers during the championship games
The support continued even after the loss. I think our recent success has raised morale around here and everyone is carrying their head a little higher, proud to be a Wayne State Warrior.
A few tweets after the game
We recently launched the Physics & Astronomy department website. This site fits within the established Planetarium theme. Physics is one of the few College of Liberal Arts and Sciences departments that have broken away from their standard template to focus on a brand that resonates with their primary audience.
Visuals
In order to effectively pull in prospective students we had think like a student looking for a physics or astronomy degree. A large centerpiece image shows off activities in the department. The goal is to attract a student by showing things they could be working on if they enroll. We made sure to also highlight the related programs in promotion buttons on the left hand side. These are supporting reasons a student would pick Wayne State over others schools.
As we evaluated the offerings of the department we ran in to a little confusion about which degrees were offered at each level. We set out to solve this with the new design by highlighting the degree types on the homepage in a multi-column view. In addition, we have a more detailed table on the programs page. This allows a student to see what is available at a glance without having to struggle to find information.
Content
Program descriptions and course listings were on the top of our needs list. Without an accurate and complete description and list of requirements, students won’t be confident in their decision about applying to the program. Creating confidence is the main goal of the content on this site. We ensured every page was hand transferred to its new location and revised for accuracy.
Extending beyond the Web
As an added bonus to using the main university CMS and events calendar is the ability to extend their information beyond their website. Events get promoted across multiple Web areas including the student portal, Today@Wayne newsletter and mobile app. The physics department also has a digital sign in their space that promotes local news, events and features on faculty. All of this information pulls from the same place and on the same schedule so there is no need to enter news and events more than once.
Visit the new Physics & Astronomy website at: http://physics.wayne.edu/
This weekend the Computing & Information Technology (C&IT) department upgraded the power in the data center. An explanation of the reason for the upgrade can be found at the ProfTech blog. In addition, C&IT has an announcement of what services were effected on their website.
How this effected the Wayne State Web
In short, this meant every website hosted in the main Web server environment would be down. Basically shutting our visitors out for 10 hours. This included the homepage, admissions website, application, events calendar, api, and content management system, just to name a few.
The down time user experience
It’s never a good experience when you click on a dead link. C&IT brought us in the loop early and we tried to come up with a plan to keep the servers online during the maintenance period. Unfortunately the entire datastore would be down, and moving a read only version to our off campus would take longer than the maintenance period itself. We decided a single maintenance page made the most sense for the time of day and number of visitors that it would affect.
We designed the page based on the promotional images we used around campus to warn students/staff about the maintenance. We kept it simple and gave the user some calls to action directing them to additional information. Below is a screenshot of the page.
The maintenance screen
“Have a little fun”
If you notice on the page there is a second link to “have a little fun“. We wanted to give anyone who was unfortunate enough to land on the dead end page something to do to pass the time and show a little personality.
One of our former developers, Nick West, was playing around with javascript and gaming a while back and came up with this exploding W page. We passed it around internally for a while but never had a chance to use it publicly. We thought this would be a perfect opportunity. With his permission, we added it to our maintenance page to see how many people found it.
During the maintenance period only ~9% of visitors clicked through to the “have a little fun” and spent an average of two minutes on the page. We expected about this percentage and amount of time on the page, but I explain why the actual quantity of visitors was quite a bit lower than we expected below.
Lessons learned
The goal was to have this maintenance page come up when any page was accessed with a “503″ (the server is temporarily unavailable) response and a “retry-after” so Google and other search engines didn’t index the temporary page. Coincidentally an article was posted on SEOMoz just days before our downtime which outlines the best practices for handling maintenance situations.
Everything seemed to be planned well for the maintenance but we encountered two issues which prevented us from analyzing the downtime completely.
- The .htaccess file didn’t get included in the files that were sent to C&IT. (completely my fault for not checking)
- The Google Analytics account did not have the “full domain” filter enabled. (again, an oversight on my part)
Because of these two issues the maintenance screen was only displayed on the homepage of each domain, not on every single file accessed. That cuts out a major chunk (like 95%) of the traffic to our server and potentially hurt some page ranks. Lastly, the oversight of the “full domain” filter in the Google Analytics prevented us from seeing exactly where the traffic was from. Seeing just “/” and “/w/” give us absolutely no insight.
Test, test, then retest
In the end we were glad to have at least some explanation of the down time up, but because of these two issues I don’t have much insight to share here. I am taking this situation as another opportunity for the importance of testing and retesting. Having a dry run of any IT or Web related activity may take a little extra time but in the end will produce the best results.
View the maintenance page: http://wayne.edu/maintenance/
Have a little fun: http://wayne.edu/maintenance/w/












