OU Web Communications - eduWeb 2011

Editor's Notes

• #2: ERIN\n
• #3: ERIN\nI am Erin Yarbrough - Director of OU Web Communications and this is Amanda Toohey - our Migrations Manager. We like to have fun during our presentations as much as we can, so we thought we’d share some embarrassing facts about ourselves with you.\n\n\n
• #4: ERIN\n
• #5: ERIN\n
• #6: ERIN\n
• #7: ERIN\n
• #8: ERIN\n
• #9: ERIN\n
• #10: ERIN\nThe University of Oklahoma is abbreviated actually to OU, not UO. I know. It’s confusing.\n\nWe are a division 1 public research University, located in the awesome town of Norman, OK with two other campuses across the state, we have about 30,000 students and have this little football team you may have heard of on ESPN.\n\n\n
• #11: ERIN\nI’m passionate about OU and so are our fans. Here’s a short video intro to OU.\n
• #12: ERIN\nI’m passionate about OU and so are our fans. Here’s a short video intro to OU.\n
• #13: ERIN\nI’m passionate about OU and so are our fans. Here’s a short video intro to OU.\n
• #14: ERIN\nI’m passionate about OU and so are our fans. Here’s a short video intro to OU.\n
• #15: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #16: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #17: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #18: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #19: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #20: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #21: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #22: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #23: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #24: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #25: ERIN\nThis is our team. We’re all a little quirky. Together we’re just plain weird sometimes.\n\nWhen our office was created in 2007 we were charged with re-architecting the OU web and focusing on branding, user experience and communication for prospective students, current students and alumni.\n\nOut of these responsibilities we’ve taken on quite a few projects - OU Social Media, Web Guidelines, The OU homepage, a Content Management System, Student Portal, Campus map and campus calendar\n
• #26: ERIN\nSo... Before our department was created in 2007, our president asked a consulting company to conduct an audit of the ou.edu domain. Well, we received a D-\n\nOut of this terrible score, the office of Web Communications was born. The president tasked us with completely overhauling the OU web, specifically focusing on the target audiences of prospective students, current students and alumni. We had a lot of work ahead of us.\n\nAnd, i know this is in the Information Architecture track, but i wanted to make sure to show you what our office is doing as a whole since that’s one thing I’ve always been so interested in - the projects and organizational structure of web communications teams.\n
• #27: ERIN\n\n
• #28: ERIN\n\n
• #29: ERIN\n\n
• #30: CASSIE\nManage content for current students\n\n
• #31: CASSIE\nKam and I produce videos, but we also promote student-produced videos and send cameras with students who are traveling abroad to capture their inernational OU experience.\n\nWe’ve also recently given a new student a camera in order to track her journey through move-in day excitement.\n\n
• #32: CASSIE\n\nUsers get really excited about football, obviously, but our athletics dept also has their own page. We try to focus on building the relationship and encouraging fans to post photos and interact on the page. We build the community with an informal dialog.\n\n
• #33: CASSIE\n\nA new project we’ve taken on is to create fan pages for incoming classes. Students were creating these on their own, but having an official channel allows OU departments to feel ownership and contribute content such as financial aid deadlines and promote communication between prospective students. Currently they’re all excited about their new room assignments and connecting with suite mates and floor mates throughout the summer.\n\n
• #34: CASSIE\n\nWe support colleges and departments creating their own facebook pages and help them brainstorm and give them guidelines and recommendations to manage. Of course we’re always asking the question “why do you need this” because departments shouldn’t just feel like just because they can they should.\n\n
• #35: CASSIE\n\nWhile facebook does push directly to twitter, we do create unique messages for this audience - mostly we interact with uofoklahoma followers.\n\nFor example, during our student orientation camp last summer, I had the search up for Camp Crimson. I noticed taht a girl was upset that camp crimson was full. I recalled seeing that an extra session was added for overflow - i was able to confirm there was still room and give her that information. She was able to go to camp crimson and then tweeted about how excited she was.\n\n
• #36: CASSIE\n\nThis is a fairly new endeavor for us. We’ve had it about a year - we’ve done small giveaways. For example when a new OU IT store opened, we gave away small prizes to the first 5 people that checked in. In the future we plan to do more with campus incentives and encouraging departments to get involved.\n\n
• #37: CASSIE\n\nThis is very similar to Foursquare - based out of Austin. They’ve been a pleasure to work with. We have more foursquare users, but gowalla is gaining momentum as well. The Sooner Gallup tour takes students through an unofficial tour through OU and they’re awarded a badge when they complete. All of the icons were created in partnership with Gowalla. They created these from photos we sent.\n\n
• #38: ERIN\n\n
• #39: ERIN\n\n
• #40: ERIN\nthe OU web prior to 2007 is what we like to refer to as The Wild West. There were some crazy and radical ideas OR people who didn’t want to see any change at all and there were probably even a few bar fights. Every department, college, committee, event, you name it, had their own website. There would be admissions deadlines, dates for finals, policies and requirements scattered all over the place and if the original information changed, there would be no way for site owners to know, so that left a lot of incorrect info out on these sites. \n\nInconsistencies and outdated information also was a huge issue to to the fact that every site had a “webmaster”. One person who was technical enough to update the site by collecting content from others - or not - whatever they wanted to do. \n
• #41: ERIN\nAlso, since student help is so cheap, many departments would use students to manage their sites. But, what happens when Ashley graduates?\nCLICK\nAll of a sudden you can’t change your site until fall when you can find the next student webmaster.\n\nSo the first thing we did when our office was formed in 2007 was purchase an enterprise-level content management system to help us combat some of these issues on campus.\n
• #42: ERIN\nAlso, since student help is so cheap, many departments would use students to manage their sites. But, what happens when Ashley graduates?\nCLICK\nAll of a sudden you can’t change your site until fall when you can find the next student webmaster.\n\nSo the first thing we did when our office was formed in 2007 was purchase an enterprise-level content management system to help us combat some of these issues on campus.\n
• #43: ERIN\nThe CMS we chose was Day Communique. And have re-designed the OU homepage a couple times during this period.\n\n
• #44: ERIN\nThe CMS we chose was Day Communique. And have re-designed the OU homepage a couple times during this period.\n\n
• #45: ERIN\nThe CMS we chose was Day Communique. And have re-designed the OU homepage a couple times during this period.\n\n
• #46: ERIN\nThe CMS we chose was Day Communique. And have re-designed the OU homepage a couple times during this period.\n\n
• #47: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #48: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #49: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #50: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #51: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #52: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #53: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #54: ERIN\n\nSo we purchased CQ4 in June ‘07 and...\n\nCLICK\n\nmigrated to CQ5 fall ’09\n\nCLICK\n\nCreated a calendar and map in CQ5\n\nCLICK\n\n-I think you could classify our office as the unruly teenager now…\n\nWe still have phases of Map and Calendar to complete and who knows what else we’ll decide to cram into our project timeline\n
• #55: ERIN\nBefore we get too much further into how we migrate sites and get buy-in on campus, I should probably mention how we fund projects in our office. OU Web Communications has the extraordinary benefit of being able to offer all services we provide - including migration into the CMS - completely free to departments. We are funded by our state regents and the President made a big deal about us not charging for services when Web Communications was created. We are a part of the Administration and Finance division at OU - which means we are separate from both IT and Public Affairs. We are able to partner with each of these departments and collaborate with other departments on campus because of this. We know that not every school is able to create such a harmonious setup in their department structure, but this is something that has been invaluable to us.\n\nSince our President wanted sites at the University to use these services and resources, he decided that providing them free would allow us to create more buy-in on campus, which has proven quite true.\n
• #56: AMANDA\nThe primary reason we brought in a CMS was to help with site management. So, we made a list of about 75 of the highest priority sites and offered them migration into CQ first.\n\nWhen we migrate a site into CQ, there are certain steps we follow to make sure we’re helping these departments overhaul their current site. We never migrate over a site exactly as-is. This is an opportunity for us to take all of these steps and really evaluate the departments’ needs and growth opportunities as well as give them the opportunity to learn the system by figuring out what they do and do not want to migrate into the system.\n
• #57: AMANDA\nThe first step we take is to help departments organize their content. This gives them a really good overview of what content they currently have and allows us to help them utilize some common organization structures for their site. \n\nThis gives us the opportunity to find common taxonomy and site organization - not just with OU, but also with competing schools. We know that prospective students and parents will be navigating through many schools and programs, so we want to make it as easy as possible to find information.\n
• #58: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #59: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #60: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #61: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #62: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #63: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #64: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #65: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #66: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #67: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #68: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #69: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #70: AMANDA\nOne of the important pieces of Information Architecture is how that fits into the navigation of a user. We’ve standardized some navigation placement so that when users are going site to site, they can expect some common elements in the same places on each site.\n\nWe place topical navigation in the left column and navigation for specific audiences along the top.\n\nAnother important piece of Information Architecture is using common navigation items that are familiar from site to site as well as between universities. For example, we recommend the use of terms like “programs,” “prospective students or future students” and “degrees” \n\nFinally, the best way to call attention to important pieces of your information architecture are through calls to action. We’ve encouraged departments to direct their users to the most important information through steps, action verbs and placement.\n
• #71: AMANDA\nThe approach we’ve taken to implementing this system is to require a few things for our branding and common user experience efforts, but to allow departments their own look and feel. We require some OU elements such as a global header, left navigation and a global footer for consistency, but how this is styled is really up to the departments. We start with a creative brief and then the WebComm web designer takes that brief and creates several design options for the departments to choose from. \n\nThis is the fun part for the departments and really how we were able to create excitement and buy-in for the CMS in the first place - because we were offering design resources - free to the department.\n\nNow - I want to mention that there are schools out there who have implemented CQ as one overall University design and Information Architecture instead of breaking up the content into departmental sites. They’ve been able to pull over an incredible amount of work - you just have to decide going in how you want to approach the project. Each approach has pros and cons.\n
• #72: AMANDA\nAnd, since content is key, some departments who do not necessarily need or want a custom design are able to use a quick start template. This option offers less flexibility with design and components for content, but allows departments to get in to the CMS quickly and easily.\n\nFor custom designs, the next step is to move into the development phase.\n
• #73: AMANDA\nThis phase requires a developer in our office to take the custom design and build out the CSS framework for the design. This does not affect placement of content, layout, content, etc. All of that comes in the content phase and is completely up to the department.\n
• #74: AMANDA\nThere are 10 people in our office - so we don’t exactly have time to train everyone who migrates into the CMS. Trust me - we tried. So now we conduct all of our training through online videos. Yours truly barricaded myself in my office for 3 days and recorded all of our training videos. They need to be updated and they do take a bit of planning, but in the long run - online training has definitely been worth it.\n\nOur migrations manager meets with departments weekly during the migration and then she can answer any questions they might have or show them new tricks or tips as she sees the need. We found that even if we offer more in-depth training up front, there’s only so much info our authors can absorb in one sitting. We found that the initial training plus Q&A sessions really solves the training need well.\n
• #75: AMANDA\nThe department is required to migrate all of their content into the CMS themselves. We will not help with this part for a couple reasons. \n\n1) They know this content better than we do. This gives them an opportunity to see what content is absolutely necessary, updated and in the right place. This is the best way to do a site audit for content - because when you’re copying and pasting text, you really only want to do the minimal amount of work.\n2) If we make them put in the content the first time, they’re now experts in authoring content in CQ - so it’s a good way for us to make sure the department knows how to stand on their own after go-live.\n
• #76: AMANDA\nAfter content migration and some audits of content and requirements, we push the site live.\n\n\n
• #77: AMANDA\nAfter content migration and some audits of content and requirements, we push the site live.\n\n\n
• #78: AMANDA\nAfter content migration and some audits of content and requirements, we push the site live.\n\n\n
• #79: AMANDA\nAfter content migration and some audits of content and requirements, we push the site live.\n\n\n
• #80: AMANDA\n\n\n
• #81: AMANDA\n