HighEdWeb Michigan – Wayne State University – April 20-21, 2015

register-nowRegistration is now open for the 2015 HighEdWeb Regional Conference in Michigan to be held at Wayne State University April 20-21! This is the regional, personal development opportunity you’ve been waiting for.

The cost to attend HighEdWeb Michigan is only $85, which grants you access to:

  • A full day and a half of dynamic presentations by higher ed web professionals, many of whom come from your peer institutions
  • One much-anticipated Keynote presentation
  • Two breakfast networking opportunities
  • An evening exploring downtown Detroit with heavy appetizers and networking
  • Conference swag
  • Swagger (the satisfaction of knowing you’re on the cutting edge)

Space is limited, we have sold out quickly each year.

Register today! HighEdWeb regional conferences are a great venue for attendees to join and benefit from great conversations that help them when they get back to the office. We anticipate a full house this year, and would like you to be a part of this incredible event.

The Michigan Regional Conference of the Higher Education Web Professionals Association is delighted to introduce our keynote speaker, Carl Erickson.

Keynote: Carl Erickson

Keynote: Carl EricksonCarl Erickson is the president and co-founder of Atomic Object, a 50-person software product development consultancy with offices in Grand Rapids, Detroit, and Ann Arbor. Atomic Object builds web, mobile, desktop, and device software products for clients ranging from startups to the Fortune 500.

Before founding Atomic in 2001, Carl was a VP of Engineering at a failed dot-com startup (briefly), and a university professor (not so briefly).

Carl also shares his experience on his blog Great Not Big – Experiments in Running a Small, Innovative Company.

Travel & Lodging

Lodging available from $169/night high atop Detroit on the riverfront. Limited HighEdWeb room rates expire on March 26th. It doesn’t cost up front to reserve your room, ensure you have a place to stay today.

Questions? Contact the HighEdWeb Michigan committee at hewebmi@gmail.com. Follow @hewebMI on Twitter for updates and information about the event, and join the conversation with the #hewebMI hashtag.

See you in Detroit this April!

Next Web workers meeting – Feb. 6, 2015

RAVPDo you manage a school/college/departmental website that represents the university? This meeting is for you.

Come share your successes, failures, questions, and lessons learned with other Web workers from around campus.

This meeting’s agenda includes:

  • Elliot Polak talking about the recently redesigned Library System website and how their team has worked to improve the site since the initial redesign in August.
  • Nick DeNardis talking about front-end workflow and speed optimizations.
  • Round table

Everyone is welcome and encouraged to share their experiences.

Feb. 6 at 10:30 a.m. in the Simon’s Room, 144 Purdy Library

RSVP is not required but suggested.

Taking action requires knowing the next step

Having a clear next step is essential to someone taking it. Next steps are easy to find online, banners, large rounded corner buttons and “Read more” links seem to be everywhere. But next steps go beyond the Web, if you have a problem with your home Internet, the next step is probably to call customer support. When you know the source of the problem it’s easy to know who to call.

Decentralized Web

Not all next steps, though, are easy to determine, especially in a decentralized Web environment like we have at Wayne State.

I recently saw a demo for a product called SiteImprove which aims to help automate quality assurance on a website. I was impressed by the product and mortified by the results at the same time. In the 1,700 pages that were part of the demo we had 445 broken links and 180 misspelled words. I expected some, but not that many issues with our site. I want to make it clear this isn’t an endorsement for the product, I have not used it, just received a demo.

I bring it up because it opened my eyes to a major problem with the decentralized Web, and specifically with “crowdsourced” Web content management, which is a more fitting description for the WSU environment.

Lots of eyes but no one speaks up

We get millions of visitors each month. A good chunk of them are internal audiences who read the content on our pages. I’m willing to bet that people are seeing these misspellings and broken links but they don’t know who or how to tell someone about them. There is the old trusty “webmaster” email address and we do get a fair number of emails there, but they are often from students who stumble on broken links they need and it is their last resort. Obviously we don’t want prospective students to get to this point.

Most often someone on campus has interacted with one of us in the Web department to set up their website. Which means they probably interacted with me, a designer, a developer and a content administrator at the very least. They know the drill, and that the content of a website is the responsibility of the department. So they often don’t think of contacting us to fix it and although we ensure the “Contact Us” area is prominent on every website it is often used for student recruitment and there may be many hoops before messages get to the Web person in the department.

The next step to alerting someone of the problem isn’t clear, therefore problems often don’t get reported.

Who’s responsible for QA?

At the end of the day, the Web Communications department is responsible for the overall user experience on the Web. There may be a lot of factors that go in to what is actually produced but if there is a problem we are charged with fixing it. Although the content on every page isn’t originated by us, we need to ensure it building the university brand instead of hurting it.

How to report a problem

I have posted in the past about how we handle dozens of support requests per day without a ticket system and that has worked well for the past few years. We are now employing the same technique to our phones. Everyone in the Web department now has a single phone number. This way if anyone is out of the office or away from their desk the phone can still be answered and get handled in an appropriate timeframe. If someone leaves a voicemail it goes to our group email account that everyone sees. It’s been a week so far and the simplification has really helped to filter all requests through one person, our project manager, and only assigned/disrupt a staff member when they are needed.

The Web Department is now acting as a single point of contact for the campus community to know their next step. They no longer have to remember a staff members name, phone number or email address. Once a problem is reported we are able to determine who is the owner of the website and the quickest route to get it fixed. We will do all the leg work to ensure it gets corrected even if the website isn’t in the main university system.

But what about the public?

The process for the public to alert us is a little trickier. In the past if we added a feedback form or email address to a website as a “feature” it tends to get used by people who simply can’t find information or to ask a basic question. This would flood the IT staff with general questions instead of actual problems. The easier it is for the visitor the contact someone the more likely it is for them to use the contact info instead of using the website to find the information they need, they often look past the purpose of the form. That being said we are hesitant to put a “Report a problem” link on the page, even if it only shows if the visitor is on campus.

We are currently testing different options and should have a solution in the next few weeks.

Contacting Web Communications

Phone: 7-9707
Email: web@wayne.edu


Welcome Daniel Greco, Web Communications’ new graphic designer

The last few months we have been looking for a Web graphic designer to fill the spot that our previous graphic designer left. We believe we have found someone who will not only fill the position but bring a unique eye to our future designs.

Welcome Daniel Greco!

Daniel Greco comes to us from Michigan State University and The Awesome Mitten. His background is in graphic design and photography. Daniel’s work at MSU has positioned him to understand how to juggle many audiences within a single identity manual. His work outside the university setting has allowed him to excel at focusing on solving interesting problems through design. He has also been involved with creating mobile experiences that interact with current and prospective higher education students.

We think Daniel is going to make a great addition to the Web Communications department and the university as a whole.

Advancing the Web

Daniel will be working with Rolaine and the other graphic designers in Marketing to continue to evolve the university identity and bring it to life on the Web. Over the next few weeks you will start to see more of his work and more than likely work with him in person. He also will be focusing on bringing our mobile experience in to its second revision with a focus on student recruitment.

Let’s give Daniel a Wayne State welcome!

Help bring a two-day responsive Web design workshop to Detroit!

Build Responsively

Responsive Web Design

“Responsive design” is a subset of a larger concept which is called “Adaptive design”. When talking about responsive we refer to the layout only (Ethan Marcotte, fluid grids, flexible images & media queries). (source)

What is @brworkshop?

Build responsively is a moving workshop that focuses on Responsive Web Design. The talks start with the basics and go on to the advanced. A wrap up of the Cincinnati is online with the presenter slides if you’re interested.

This is a great opportunity to show the impact of the Web community in Detroit. Our city is going up against Pittsburgh, Chicago, Nashville, and others. Take just one minute to show your love and support for Detroit and RWD.

All it takes is a click and a tweet.

Hiring: Web graphic designer with a passion for user experience

Are you a graphic designer with a passion for user experience? We’re looking to fill a full time position left vacant by Joy Reed (which basically means you would have some big shoes to fill). We’re looking for someone who has primarily worked in the digital space, a traditional graphic design background is preferred.

This person will be a member of our dedicated Web Communications team and be responsible for the graphic design in complete Website redesigns, have an influence in the user experience across the Wayne State Web, both public facing site and the internal tools we create.

Our department’s responsibilities extend beyond the Web in to digital signage, html emails, mobile apps and illustrated icons. Lastly, this person must maintain, advance, and consult with the campus community on brand consistency.

Preferred qualifications:

  • Solid understanding of working with-and designing for-web applications.
  • Able to rapidly prototype static wireframes or use other dynamic prototyping tools.
  • Experience working on large-scale higher eduction websites.
  • BA/BS or above in Graphic Design, Information Design, or other visual arts; strong technical understanding a plus.
  • Minimum of 3+ years experience designing web-based products for a consumer-oriented website.
  • Ability to act as a leader in communicating conceptual ideas and design rationales, all within a user-centered design process.
  • Able to work and communicate effectively in a cross-functional product development team, and present ideas and designs effectively.
  • Self-motivated to prioritize and manage work load, and meet critical project milestones and deadlines.
  • Able to collaborate with colleagues to develop and enhance design standards.
  • An effective problem solver who comes up with creative solutions and considers many alternative solutions to each problem.
  • Fluent in HTML/CSS/XML, or full knowledge of associated capabilities/limitations.
  • Maintain an overall university brand across various mediums including digital signage.
  • An understanding of responsive Web design.

Think you have what it takes?

Check out the official job description at job.wayne.edu. posting #038624.

Or know someone who would be perfect? Be sure to pass this along.

So you want an HTML newsletter?

The types of projects our department takes on seem to go in waves. A bit of a history lesson takes us back to an abundance of websites which pushed us to build the CMS. The many events that followed gave us the idea to write and centralize them all in to a university events calendar. Then came the RSVP’s for those events. We got fed up creating hundreds of forms so we wrote an RSVP system for the events calendar. After that the campus community could maintain their own websites, and create events and RSVP’s by themselves. They then asked us to create pretty HTML emails to announce all of these components and we did that for a while before crafting the self- serve HTML email creator.

Everything goes digital

Now we are on the age of transitioning traditional print newsletters to digital pieces. These are a little more complex than the standard email and sometimes connect to a broader website with more information. In the last four months we have literally transitioned more than ten complete print publications to online editions. I would love to say that in those four months we created a self-service system for the entire campus to create and maintain publications, but I can’t. They all seem to have some unique factor that required individual attention.

Multiple flavors

Requesting a new HTML newsletter can result in a 2 hour or up to a 40 hour project. It’s important to know what you need before starting the process. Let’s walk through the process of the newsletter request and I hope I’ll be able to shed some light on the reason for the complexity.

Simple single column email

The most basic email is just a single column with a single message and any action items go off to existing websites. The types of emails have a custom header that identifies your department or group and is reusable at your leisure.

Here are a few examples of single column emails we have done:

Multiple column email

Typically a multiple column email is required when there is a single message that needs to be communicated and the content warrants “action items” on the side. These can be: upcoming deadlines, buttons for next steps or just “for your information.” They’re a little more complex but offer some flexibility to highlight multiple items “above the fold”. (BTW, there is no fold on the Web.)

Here are a few examples of multiple column emails we have done:

Multiple column newsletter

Using the same format as the multiple column email the newsletter takes it one step further and keeps a consistent format but with categories and articles feeding in to compile a complete email. Typically the format is set up and each month/semester/year a new “publication” is created which consists of article titles, teaser descriptions and links off to more information.

If the links for each article go to existing stories already published on the Web it gets the user to interact with multiple areas of your website and possibly explore things they otherwise wouldn’t have without being prompted by the email.

Here are a few examples of multiple column newsletters we have done:

Newsletter Web page

Lastly the most complex and time consuming is the HTML newsletter that has a stand alone website which features the full text of each article and is organized like a newsletter with editions and archives. This approach is really driven by the print mentality of compiling an entire edition of articles and publishing the entire thing at once. It wraps up the email and website into a single package for the user to experience. One of the downsides, just like a printed newsletter/magazine is once the user receives it and browses through, they typically recycle it or close the window and never come back. Their only reason to come back in the future is when their next email comes in. It isn’t “sticky” and doesn’t build continuous engagement, but in the end it’s what most traditional writers are comfortable with.

Here are a few example of newsletter websites that we have done:

Thinking about requesting an HTML email?

Make sure you have thought through how you want it to work and be prepared to answer some tough questions by our team. Just because “email is free”, aka you don’t have to pay postage, it doesn’t mean that your audience will engage the same way they have in the past.

Future of Web Design – Responsive Web Design

I just recently went to Future of Web Design (FOWD)  in New York City for an amazing web conference. Besides the amazing speakers, friendly atmosphere and cool city life, the conference had a reoccurring theme: Responsive Web Design.

Now “Responsive Web Design” is by no means a new concept, but it has speedily becoming a web design standard.

Here are the basic premises behind the idea to achieve Responsive Web Design:

  • Design must be flexible to the users behavior and environment
  • Use flexible grids and layouts
  • Use flexible images that will adjust to each view
  • Use smart CSS media queries to adjust to the users resolution size
  • Just one URL, no more, m.mobilesite.com

Food Sense Example

Responsive Web Design - Foodsense

This is a great example of Responsive Web Design – http://foodsense.is/.
To see this in action open the link on a desktop browser and slowly drag the browser window size smaller. You will see the layout elements adjust on the page to the new width.

Other great of examples of Responsive Web Design:

As web design and development evolves into the future, with multiple devices such as smaller laptops, tablets and smartphones, Responsive Web Design seems to be the best solution for the moment.  We can no longer just design for a couple of devices, we must accept that the amount of devices and resolutions are going up dramatically. I will leave you with one of my favorite quotes from the conference:

“If its not responsive design, its not web design” – Andy Clarke

Good Resources on this topic:


We’re Hiring: Full Time Web Developer

We are hiring! The Web Communications office is looking for an in house Web Developer. It’s not often we put a call out for new staff but with Nick West’s departure we are in need. Our department started six years ago with little staff and resources. Almost everyone in our department started as a student and worked their way up (myself included). It’s not often we get the opportunity to hire from the outside.

The job

We take the Web seriously. The position at hand is responsible for a third of all the code that gets published to the public Web server. This ranges from core back-end API functionality to front-end HTML, Javascript and accessibility. With three developers the projects are distributed evenly so everyone has the opportunity to work on something new. We are a very collaborative environment and this position has the opportunity to affect the direction of all future Web projects. If you have read our blog in the past you will know we push out a lot of sites, about one per week. All sites are created from the ground up, completely by hand. The Web is a craft and we make sure we build all the tools needed to do it as streamlined as possible. This position has the opportunity to build and maintain these tools that impact the entire institution, not to mention work with an amazing team.

Primary Web property responsibilities


  • LAMP
  • PHP Simpl Framework
  • jQuery
  • Load balanced dev/prod environments
  • 400+ websites using centralized tools
  • SVN

Official duties

  • Translate functional requirements into Web applications
  • Centralize and maintain existing code bases
  • Prepare test plans for Web Applications
  • Design database schemas and develop database scripts such as SQL
  • Serve as primary resource for units university-wide regarding the code and appearance of unit Web pages. Administer and provide training in content management tools, control access, review sites for adherence and conformity to code and design standards and resolve related problems.
  • Serve as liaison with IT personnel campus-wide to identify and resolve Web page related problems. Work with clients, designers and vendors to ensure established standards and expectations are met.
  • Develop and implement mechanisms and processes designed to evaluate the effectiveness of university electronic communications. Provide analysis of collected data and submit reports and recommendations as requested.


  • HTML + CSS: Mastery of cross browser CSS and HTML
  • JavaScript: Proven understanding of Javascript fundamentals, plus experience working with AJAX
  • PHP + MySQL: Experience building data-driven web applications using PHP and MySQL. Solid understanding of relational databases required.
  • Experience working with Web Services and associated languages: SOAP, REST, XML, JSON, etc.
  • Good knowledge of web standards and trends
  • Ability to learn and thirst for knowledge
  • Test/Behavior Driven Development experience is a definite plus
  • Graduation from an accredited college or university or an equivalent combination of education and/or experience. Major concentration in computer science preferred.
  • Excellent writing, editing and communication skills.
  • Ability to establish and maintain effective working relationships with units university wide.

How to Apply

Please do not send resumes directly to me. You must apply before August 17, 2011 at jobs.wayne.edu. Posting #037995

CASE District V 2010 Conference Wrap Up

A few weeks ago I attended the Case V Conference in Chicago. They asked me to present about Flexible Web Branding, the Case Against Single Web Templates, it went really well and the slides are now posted.

I mainly attended the Web track and wanted to run down some key takeaways from the conference. Below are my notes from each session, they are not proofed so please ignore incomplete sentences and typos.

Beyond Facebook and Twitter: Using Social Media in a Multi-Channel Campaign to Recruit Students, Raise Money, or Build Awareness for Your Institution

  • Everyone already has their social media accounts setup, now what.
  • Making it part of a strategic campaign is a whole lot more difficult
  • Social media definition
    • Web-based tools user for social interactions
  • Social media tools are a way to connect with different groups of people on a platform where they spend their time
  • Social media Campaigns
    • A focused effort to achieve goals using a variety of channels appropriate to the results sought
  • Blend of offline and online channels
  • It’s easy to get from your blog to flickr, to twitter, to your blog to facebook
  • Amusing ads in the student newspaper
    • Pig got kidnapped, ads that were amusing
  • Facebook will never replace your website.
  • Powered by Orange
    • Budget crunch in Oregon
      • Ad budget is getting cut
    • web, blog, google map, sm, merch, real world, personal
    • Spotlight on a business
      • Feature story
      • Surfaced business & alumni they didn’t know existed
    • Post things that other audiences would be interested in
      • Will get your stories into non-typical audience hands
    • Initial purpose was to get more attention for Oregon State
    • Extended into a LinkedIn group
  • Northfield Mount Herman
    • Budget cuts
    • Went from 6 to 5 staff
    • Reorganized dept and roles
    • Now has a social media person
    • NMH Book
      • A connector for their social media presence with their website
    • Facebook was the most likely way someone getting to their website
    • Posts getting the most interaction
      • In house video
      • Emotional attachment
    • Using WordPressMU
      • Started out with existing bloggers
      • Capital Campaign
        • Comment about why you liked NMH
      • Promote the blogs only after they prove themselves
    • Using Flickr to allow parents to download their child’s photos
    • YouTube and Vimeo
      • Vimeo has higher quality videos
    • Engagement is the strongest reason to do this
      • Build relationships
      • Don’t over structure messages
      • Every social media message doesn’t need to have a call to action
    • Rule of thirds on social media: 1/3 about yourself, 1/3 sharing, 1/3 conversation.
    • Captioning videos
      • Not really doing any now.
      • Suggestion: Start with the YouTube default and use student minions
  • Matt Mertzberger has a great policy that he developed for social media on campus
  • Facebook is about connecting with friends
    • Ads are not going to impact them

Brand as Transformation: Attracting Your Best-Fit Student


  • The change in enrollment was due to marketing
  • They never told their story
    • This was the difference in how the school was perceived
  • Family First
    • People go out and people tell you thing that you don’t know
    • Tell the family first, don’t let people get blindsided
  • Make it personal
    • Do it with each other, not just an external audience
  • Central voice
    • In writing
    • In speeches
  • Service never ends
  • How they did it
    • Tuition reduction
      • Causes window shopping
      • Big burst in viewers
      • Everyone got the scholarship reduction
    • Wave the banner
      • Marketing
  • Get the tuition information out there early
  • 3.38% – add the detail so people think you struggle over it

Capital University

  • 2008 lost their focus
    • Chasing their competitors
    • Loosing money
  • Provost became president and turned it around
    • Cut costs
    • Figuring out who they are
  • Best student: Highly focused kid
    • Not the average liberal arts college student
  • Who they are
    • Capital University is..
  • What are the benefits
    • Helps students get started in a career
  • Where are they going?
    • Changing the graphic from columns of departments
    • To a circle that shows everyone is connected
    • Students start in the middle and move their way out
    • No hierarchy to it
  • Tag line
    • Ask. Think. Lead.
  • Campaign that ensued from all this
    • “Will You?”
  • Social Media story site
    • Existing students tell their will you story?
    • Identified the URL for the site around campus
    • Lead them to a video unscripted of students
    • Allowed students to tell their story
  • The video made all the difference
    • 80% of current students added their story
  • “I WIll” admissions office has a poster board
    • Students put up photo and story
    • Given them back at graduation
  • Virtual tour
    • Student prospective tour
    • Imports photos from facebook
    • Pop quiz
    • Then gives them a first day agenda
    • Photos scrolling are based on that agenda
  • Acceptance letter
    • “Size of a little says something about the contents”
  • Living the brand
    • 6 mini workshops with nearly 200 student, factuly and staff
    • Train the trainers

Higher Education: The Toughest Gig in all the Web

University at Buffalo

  • Not printing class schedule
  • Not printing catalog
  • Save $100,000 per year printing
    • Money went other places
    • Not into the web department
  • 581,601 pages indexed on the main buffalo website
  • What is the bottom line?
    • Higher ed has no idea
  • Mission statement
    • Five page document
    • Reduced it down to nine words
    • “Understand the Business”
    • “Understand the User”
    • “Understand the Medium”
  • Governance
    • Higher Ed Follow federalism
  • Paradigm, your world view
  • Let their be web divisions!
    • Jeff Zeldman
  • Think like an entrentpeur from the beginning
  • Business Plan
    • “Funded to to meet every reasonable request in a reasonable amount of time”
  • “A man’s gotta know his limitations”
    • Clint Eastwood
  • 24% of people in the Noel Levitz Survey
    • Eliminated a school off their list because of a bad web experience
  • The world is flattening because of the Internet
  • SUNY
    • Going to discontinue their language programs
    • Tenured faculty are being cut
  • Books
    • Higher Education?
    • Wannabe U
    • DIY U
  • “It is not necessary to change, survival is not mandatory”
    – W. E. Deming (via @markgr) #casev

Six Sigma Approach to Website Redesign

  • Different Approach
  • Methods
    • Define priorities
    • Guide creative process
    • Minimize competing interest & politics
    • Establish the means to prove success of the redesign
    • Create a framework to monitor quality and predict changes
  • National university of health sciences
  • 65% of CASEV member colleges have redesigned their sites in the past two years
  • 1/3 of the sites will redesign in the next year or two
  • 251 CAEV institutions
  • Website redesign are often reactions to fix short term issues or problems
  • Websites use quality over time
    • Resources
      • Don’t invest a lot in between redesigns
    • Life Span
      • What we implement can’t be sustained over time
      • Expectations of the users have changed
  • “I’m drowning here, and you’re describing the water!”
    • Jack Nicholson, as good as it gets
  • Six Sigma
    • Doing superior work
    • “Six Sigma is a fact-based, data-driven philosophy of improvement that values defect prevention over defect detection. It drives customer satisfaction and bottom-line results by reducing variation and waste, thereby promoting a competitive advantage”
    • Concepts
      • Philosophy of Work
        • Processes that can be: defined, measured, analyzed improved, controlled
      • Set of Tools
        • Use of qualitative and quantitative techniques to drive process improvement.
      • Methodology
        • Rigorous approach toward problem solving.
      • Metrics
        • Specific benchmarks
    • Six Sigma Web Management is a fact-based, data-driven approach to website management (strategy, design, development, marketing, maintenance) using Six Sigma philosophy, tools, methodologies and metrics.
    • SSWM recognizes the success of a website is dependent on the Web team’s ability to articulate, measure and monitor website quality during all stages of this process
    • “Higher education websites are consensus-driven”
    • You can never have a superior website if it is built on a consensus basis
    • (Overlay the redesign timeline on the applicant, acceptance and enrollment)
  • 1. SSWM Process
    • Content Audit
    • Materials Review
    • Competitive analysis
    • Motivational assessment
    • (Find patterns)
    • Web quality layers
      • Content
      • Design
        • Drives the younger generations
      • Navigation
        • If it makes them feel like they are dumb they will leave
        • Hurts their ego
      • Technical
        • Response Time
    • Brand experience
      • Messaging
        • Do you have a message that is effective
      • Satisfaction
        • Are they happy about what they are hearing
      • Website rating
        • How are they personally rating the site?
    • Audience Intent
      • Motivation
        • Will your website get them to do something?
          • Visit, Apply, Request Information
    • New Prospect & Alumni
      • Have the same motivations but different goals
      • Prospects looking for people doing great things to aspire to
      • Alumni looking for people doing great things to relate to
    • Do this when you are redesigning
      • Then do it again six months after
    • Vendors need to stand by their product and fix it if there is a problem
    • Segment the audience types
      • Enrollment
        • Prospect
      • Sent the survey out via email
    • Lizeral software to ensure surveys are functional
    • The problem they found was the design was created by consensus
      • Current student, faculty and admin
  • 2. Top down Strategy
    • Share the data with the leadership, president
    • Got their motivations and intentions
      • These translated to the focus group questions
  • 3. Iterative Design Process
    • Started with the basis
    • Leadership wanted to go further
  • 4. Bottom up implementation
    • Web committee comes in to play
    • Not to make decisions on strategy
    • Building the pages and communicating he changes
    • Doing all the content at the department level
  • 5. Continuous improvement
    • Tools setup initially that can be monitored over time
    • Making small tweaks to design or nav every so often
    • 6 months being the least amount of time
      • Then yearly intervals