Posts in Web Services

The past two days we've held sessions to present the process of the website redesign. At the start of the redesign we had two internal goals. First, ensure the redesign was a process, not a one-time project. Second, involve the community along the way.

During the meetings we unpacked five parts of the process that have brought us to where we are:

Partner:

We knew from the start one of the biggest decisions would be to select the right partner. Several nationally recognized firms sent us proposals, and we brought three firm on campus to present their proposals in person. From these presentations mStoner stood out from the rest. The team we're working from their firm has proven to be a valuable partner.

Strategy:

Strategy included three key parts: stakeholder intake, competitor analysis, and testing. We spoke into how each of these three areas informed both the scope of the project and the design of each concept.

Concepts:

Based off the information collected in the strategy phase, three separate concepts were created by three different designers—each taking a different look at a potential Bethel website. During the meetings, we walked through each of these concepts to dig a bit deeper into the process that went into their development.

Feedback:

Lastly, we presented results from the survey that was released to four main groups: prospective students, current students, faculty/staff, and alumni/parents. Based on the feedback from each of these groups, the steering committee selected concept two as the new face to Bethel's website.

There were a lot of great questions and comments discussed during the meetings. If you were unable to attend, scan through some of our past posts for information about where we've been. If you have additional comments or questions, feel free to send me an email (vedmic@bethel.edu).

After sending 35,000 surveys and receiving a record number of responses, the results are in:

Concept two resonated with the Bethel community as the best fit for the new website. High Res

Concept two will be the face of Bethel's new website.

The survey revealed great information about messages, designs, and how they fit together. Plus, you provided helpful feedback on how the concepts spoke to you and how well you felt they represented our community.

Record-setting survey

In the survey process, our community (prospective students, current students, employees, parents, and alumni) set two records for redesign firm mStoner.

First, we hit a record number for survey responses—mStoner has never seen so many people give feedback on a redesign survey. Second, they have never seen there be such a clear consensus—across all groups. 

Some of your general comments about concept two include:

• "It's about the student, the community, and the transformation of a student as a partner of the community."
• "It feels like there is a plan and a place for me."
• "It tells me that Bethel is a process... I really get a sense of the transformation journey."
• "Bethel helps you become who you are meant to be."

A winning combination

When asking questions about messages separately from design, our community had a range of preferences. But when asking about design and messaging paired together, mStoner has never seen a concept score so highly.

The combination of message and design on concept two seemed to have a powerful effect that resonated across our community.

Learn more about our survey results.

What's next

Web Services will work with mStoner to refine and improve concept two until it will serve as the best foundation for the new site.

We'll continue to keep you posted, so check back soon. Finally, a big thank you to all of you who took the record-setting survey—it just shows what an awesome community we have here at Bethel.

All summer we've been busy preparing Silva for the redesign.  The upgrade to Silva 2.1 was just the start.  We have a number of improvements still to make, and few that are finished and ready to deploy.  This week three enhancements will be deployed to improve existing features:

1. A popup calendar for date/time entry.  No need to remember that Silva uses an international date format -- now simply navigate and click on the desired date in the pop up calendar.
2. Dynamic reference entry. Some external sources have properties that allow references to other Silva objects to be placed using the Silva Lookup Window.  These properties are now more compact utilizing the search and edit icons that are present in the link tool.  Additionally, those properties which support multiple references will have a separate row for each reference.  Example: "Embed Silva Content"
3. Bethel-Layout metadata updates.  The Bethel-Layout metadata set had a number of properties that were checkboxes.  These are now radio button sets which enable authors to set the property as inherited, yes, or no.  Previously it was not possible to set a property as 'no' if a parent folder or publication had the same property set to 'yes'.
4. Upgrade of the "Embed a Silva Document" external source.  This external source, instrumental in enabling complex page layouts, is being upgraded.  Highlights include a new name "Embed Silva Content", the ability to embed multiple items within the same source, and styling for both the container and each capsule.

Over the past few months, our team and many other folks from the university, have felt fumigated with “strategy.”

We've had many long conversations that gave us excitement and energy, while other discussions left us with headaches and more questions.

Needless to say, the delivery of the Strategy Document from mStoner was a bright day for us—we hoped it would unlock all the mysteries behind designing and building Bethel’s new site. But once we had the document in hand and spent time looking through it, we discovered that it really held a lot of good stuff that Bethel already knew about itself and its website. mStoner just found a way to put it all together.

The term strategy document is shorthand for a huge number of pages—68, plus a few appendixes—outlining lots of details and big-picture ideas about the project, such as:

• Scope of the project
• Evaluation of our competitors
• Key messages to communicate through the web
• How our webpages will be organized
• Technical updates recommended for Silva (Bethel’s content management) and much more

Rather than having you dig through the entire document searching for gold nuggets of strategy, we’ve pulled out some key areas to share with you.

1) What We Heard From You

mStoner consultants, our friends Doug, Patrick, and Michael, flew from their Chicago office to our St. Paul campus to meet face-to-face with groups from our community.

They also spent hours in follow-up meetings by phone learning all they could about who Bethel is, what makes us distinct, and what our hopes are for the new site.

In What We Heard From You (PDF), mStoner pulls together some big-picture ideas for the project that they heard directly from the Bethel community. Take a look through to see what they found—let us know if you think they’re on track with the three main issues they plan to address.

2) Audience Overview

We know we have tons of people visiting our website and they’re all coming for different reasons. mStoner uses this section to outline who is spending time on our site and the most important things they expect to find.

Scan through their Audience Overview (PDF). Let us know if there's anything major that's missing. What are the most important things you do on Bethel’s site? What audiences do you serve and what are they hoping to find?

3) Key Messages

Beyond meeting with people from all areas of Bethel, mStoner spent time pouring through our publications, webpages, brochures, viewbooks, postcards, and more to discover the core of Bethel. From their research, they uncovered some key messages and themes that tie us together.

This is my favorite part of the strategy—for me, this is the heart of why I’m here doing the work I do.

So take a few a few minutes to read through the Key Messages (PDF). Spend some time reflecting on what Bethel is all about—I hope you come away energized about being a part of this community.

4) Measuring Success

So how will we know if we’re on the right track? How will we know if in the end we’ve got it right?

mStoner outlines some ways for Measuring Success (PDF) along the way, such as testing how students through navigate websites or getting together a focus group to talk about specifics of a design concept.

They also point to some tangible things that we can track once our new site is up and running to give us an idea of how well our new site is received—application numbers, growth in giving, increased website traffic, and more.

To keep you from also becoming saturated with strategy, I’ll wrap this up.

More is on the way as we ease out of this strategy phase and move into phase two. So peruse through this info, pass it on to others, and share your thoughts.

The web services team, along with Patrick and Brian from mStoner, ran through the first round of wireframe testing on Tuesday (6/23).

Wireframe testing is used to gather information about how users might perform specific tasks on a website. We can use the testing to see if certain features of the site make sense to first-time users and to help uncover any problems before the design stage begins.

The team came up with a lists of about 10 tasks that would be common for Bethel's website users, and then observed as prospective undergraduate and graduate students tried to complete the tasks. Each session lasted between 15-25 minutes. Some of the tasks included: finding a list of majors/minors, locating the cost of tuition, applying for admission, and finding out how to get to Bethel.

We gathered a significant amount of data by testing 18 prospective students. This data will provide valuable insight into terminology, page layout, and navigation.

Although we scribbled plenty of notes on paper, we also used an application called Silverback to help capture information during testing.

Silverback records the video and audio of a test session—and records where the user clicks on a page. When we watch the video playback of the session, it gives us two views side-by-side; we can see and hear the user (including facial expressions and any thoughts they verbalized) and we can see a replay of the their mouse and where they clicked on the page as they were attempting to accomplish the task.

The web services team will continue to testing throughout the entire redesign process.

Well, I'm sure all of you have been dying to know what a Web Services TA does all day. I've been a TA (that's Technical Assistant - not Teacher's Assistant) since the beginning of my sophomore year. That gives me almost two years of experience working with Bethel's website and learning about Silva and let me tell you, it has been a crazy ride.

When I first began as a TA most of Bethel's web content was stored on Dreamweaver. My first job ever was to finish transferring content (all of it) to Silva. Because Silva is a very different content management system (CMS) than Dreamweaver not only did transferring content include copying and pasting text and reuploading pictures, it meant reformatting each individual page to look the way it did in the old CMS. That was quite the task.

Now that most everything is located within Silva, however, my job tends to look a little different. Often I'm assigned to put brand new content on the web. I create web pages for things such as Seminary events, Focus, Heart & Mind, and Tapestry issues, NYCAMS, and much more. During my down time I work on Checkbot. Checkbot is a program that monitors Bethel's site looking for broken links. I go through and try to fix these links so they direct you to the correct place—which makes everyone happy. :)

One of my favorite tasks is Silva Training. I am privileged to work with Bethel faculty, staff, and their student workers to aid them in creating and updating their own Bethel websites. I generally teach Silva Basic Training with individuals who are taking the next step to maintain their web pages. This is my favorite because it gives me the chance to pass on my knowledge of Silva to others. After training I always encourage people to contact me if they have any questions because I know how frustrating it can be if you have a problem while working in Silva.

That just about covers everything I do as a Web Services Technical Assistant. Sometimes there is downtime and I have to search for jobs to do, but there is never a dull moment because I have a wonderful team up here in Townhouse H3.

One of the things I enjoy about my job as the director of web technology is getting to dream up solutions to peoples problems. Occasionally we get to implement some of those solutions for our team.

Last week we launched two new widgets. The first, a visual timeline that displays our progress throughout the redesign. The second is an email subscription to our blog that delivers blog posts directly to your email.  Check them out and let us know if they are helpful by commenting on this post.

In an attempt to communicate the status of the web redesign project, we wanted to spend some time recapping where we've been and where we are headed. 

Where we've come from

The past month has been very busy for our team. On top of managing the day to day tasks that come our way we've also worked on several redesign projects. The past month and a half looked something like this:

• 4/14 - 4/16 Onsite stakeholder interviews
• 4/28 Intake with steering committee
• 5/7 - 5/8 Wireframing with mStoner in Chicago
• 5/15 Wishlist meeting with CAS admissions and academic departments
  
• 5/17- 5/20 Strategy document work
• 5/20 Wishlist meeting with SEM admissions and academic departments
  
• 5/21 Intake with Web Services and presentation of strategy document to the presidents strategy team
• 5/28 Wishlist meeting with CAPS/GS admissions
• 6/3 Worked with the library on possible internal and external templates
  

Where we are headed

We have a lot of things to do. In the weeks to come we will be focused on:

• 6/8 - 6/15 Creating a collective wishlist
  
• 6/10 Launching new technical infrastructure
• 6/8 - 6/23 Working on the internal architecture of the new site
• 6/23 -6/24 Onsite user testing with mStoner
• 6/30 Second draft of the strategy document prepped for presentation
  

mStoner introduced us to a new way of looking at the web.  Its something collectively defined as the "papernet."  During our trip to Chicago we took part in a several hour cut and paste session, ultimately resulting in 10 good site templates. Our goal, to come up with the raw elements of each template while avoiding design.

Papernet Gallery

40 cups of coffee + 5 guys + 2 days and 1 gigantic whiteboard = a good start to a strategy document

Mark and I took off at 4:00 a.m. on last Thursday morning to meet the mStoner crew in Chicago.  Our object was to sus out details related to the web strategy document. We outlined global, topical, and audience based navigation.  We worked on putting together 10 of our 12 page templates, we talked about content, looked at information architecture and survived one crazy cab ride back to the airport.

All in all it was a great trip.

Mark and I will be heading off to Chicago this week to work with mStoner on the outline document that was created after the stakeholder interview sessions.

Our object is to:

• define high level site structure
• discuss messaging
• create a preliminary features list
• and wireframe potential solutions

Once this is done we will be heading back to campus to continue stakeholder feedback and further flesh out the strategy with both the Web Services team and the University.

Many of you have inquired about our content management system, called Silva, asking if we'll be getting a new one during the redesign. For some of you, the prospect of a new system is exciting. For others, the prospect is terrifying.

In light of that, Web Services is working to create a win-win for both groups. We won't be getting rid of Silva during this redesign. However, we'll be making some drastic improvements—starting with a upgrade sometime this summer that will fix and improve a number of baseline features.

Later this year, we'll roll out larger changes to the core of Silva. Please check back for announcements about these upcoming changes. I think you'll find that in the end we'll have a much improved content management system.

Thanks to all who participated in our website redesign kick-off meeting marathon this past week!

As mentioned in previous posts, we scheduled and successfully conducted 23 meetings with over 130 representatives from across the University involving students, faculty, staff, and administration in our 3 day conversation.  In addition, we had representation from CAS, CAPS, GS, and SEM...including both coasts!

Granted, this is just the first of many opportunities that the Bethel community will have to participate in the redesign process.

Based upon discovery from online surveys, onsite stakeholder interviews, public Q&A sessions, technical assessments, and numerous conversations, mStoner will generate a strategy document that outlines and defines constituency expectations, preliminary information architecture, and a project plan. More about that in the coming weeks.

We welcome your questions and feedback.  Feel free to leave a comment.

Seems the iPhone has a software solution for everything.
Need to remember where you parked your car? There's an app for that.
Need to recognize what poison ivy looks like? There's an app for that.
Need to know if the bird you're looking at is a red-faced warbler?
There's an app for that, too.

Need to know exactly what to expect in the stakeholder intake meetings?
Sorry, there's no app for that. You'll want to arrive with an open mind, and be prepared for anything!

mStoner consultants will be on campus April 14,15, and 16 in order to begin the strategy phase of our redesign process. Meeting with over 130 individuals representing students, faculty, and administration, they'll discover what makes Bethel distinctive, better understand the complexities of our institution, and begin to assemble a strategy for moving us forward.

If you can make time, please come to the Q&A session for all Bethel community members on April 16 from 11 a.m.-1 p.m. (BC468). You’ll meet Patrick DiMichele, a senior strategist from mStoner, and learn a ton more about the project.

This week will be one of the most exciting weeks of the redesign process. Let’s get ready to welcome mStoner to Bethel and help them understand who we are, why we’re here, and where we’re going.

Here are some numbers to consider.  23 meetings involving approximately 130 participants over the course of 3 days.  Any way I do the math I'm reminded that Bethel is many things to many people.  We've done our best to include representatives from across the institution when scheduling our mid-April website redesign stakeholder meetings with mStoner consultants.

If you haven't received an invitation, or if you're unable to attend one of the scheduled sessions, please plan to join Patrick DeMichele from mStoner for a Q&A session on April 16, from 11a.m.-1p.m. in BC 468.  This event is open to the entire Bethel community.

We also invite you to complete our online survey.  At last count, we've received 130 responses.  Thanks to all for offering input and feedback!

Last week we launched our first online survey relating to the redesign.  We've received 65 responses to date from students, staff, faculty, and alumni! If you haven't yet provided your 2-cents worth, please do so. This information will assist mStoner consultants gain a perspective on what works and doesn't work with our existing website. We don't expect flattery or fanfare, just the facts. Visit: redesign.bethel.edu and click on the survey link to leave your comments.

Lao-Tzu (604 BC - 531 BC) likely didn't have a website. But I believe that he understood how daunting a task it would be to redesign one when he quipped, "A journey of a thousand miles begins with a single step."

We're pleased to announce today that Bethel University will begin a website redesign!

Seems like an ominous undertaking. How does a university enter into a website redesign? How do we get started?  Who will guide us through the process? We've chosen an experienced partner to assist us as we begin the journey.  mStoner team members will be on campus in mid-April to kick-off the website redesign. They'll meet with representatives from across the institution, gather information, and offer Q&A sessions.  From this input, mStoner will help us map out a strategy plan, and determine next steps. Web Services will facilitate throughout the process.

It's not easy to select a vendor to partner with.  Its kind of like looking for a new best friend. You know, someone you are going to hang out with late into the evenings, who is going to provide constructive criticism, someone who is going to make you better then you are now.  I guess the only real difference is that a vendor gets paid.

I'm sitting here wondering to myself, why is it so hard to create good websites? Certainly it can be done.  We see examples of it every day, yet it just doesn't seem that easy. Maybe its because designing sites requires such a diverse set of skills.  One has to write like C.S. Lewis, have an aesthetic eye like Vincent van Gogh and architect structure like Frank Lloyd Wright. Put them all together and what do you get; a man named Lewis Van GoghLloyd Wright who can design good websites.

This is my first web services blog post. I want to say I am excited about what's to come this year. I'm anticipating a lot of work, but hopefully we will be able to successfully communicate what its like to work, live, teach, and go to school at one of the greatest Christian organizations in the world.