Blackboard

Surfacing Blackboard’s value proposition in the main navigation

The largest opportunity with the new global marketing platform was shifting how Blackboard connected with its prospective customers.

Originally, a prospective customer’s journey would begin with selecting their industry to dive deeper into a plethora of information about the different products and services. This experience was informative, but it didn’t make it clear that Blackboard’s competitive edge is not in any one individual product but rather in the interconnectedness of their various products, and how they come together to build a dynamic educational ecosystem, regardless of a customer’s industry. We worked with Blackboard to transition from an industry-focused navigation, originally:

To journeys that surface Blackboard’s value streams first: Teaching & Learning, Community Engagement, and Consulting Services. 

Given the importance of Blackboard.com as a marketing tool to drive revenue, we knew we needed to test our efforts in order to identify any usability issues before the site went live. To do this, we conducted in-person user testing at Blackboard’s annual user convention, BbWorld. We gained valuable insight that informed the final structure of the site navigation. Having positive and constructive real-world user feedback was essential in gaining stakeholder buy-in on this new approach. 

Now, Blackboard.com with its revised primary navigation helps connect prospective customers to the different ways Blackboard provides value to its customers. 

Empowering global marketers through a consistent UX 

Prior to the new platform, one of the major challenges Blackboard’s marketers had with the former Tridion content management system was efficiency. In the past, every page needed to be built manually by Blackboard’s internal web team. Marketers used to submit a form to the web team. Often faced with a backlog several weeks long, the web team created it from scratch as soon as possible. A draft page would be created, sent back to the marketer, and any edits would be returned in a document. This could take several days at best to release a new page or changes to an existing page. 

Blackboard marketers can now add and edit content easily while remaining on brand and demonstrating Blackboard’s impact around the globe.

After understanding this process, the different types of content needed and ways that content can be presented to support the new user journeys, we delivered a collection of over a dozen flexible components. Now marketers worldwide are able to create and edit pages on their own, reducing time to market and costs, and the web team is able to focus on other higher value-creating activities. 

Powered by a modern CMS, Drupal 8  

Blackboard needed an enterprise-grade CMS that was capable of scaling to meet their increasing marketing needs while also remaining easy for their content authors to manage. Drupal was a great choice for Blackboard as it enabled them to respond and make content and code-level changes quickly, including introducing new functionality.

The next iteration of the Blackboard brand, supported by a pattern library

The new platform provided an opportunity to rethink how Blackboard uses space and colors so their digital properties are more consistent in look, feel, and structure to their products. 

Blackboard started using color more sparingly and with greater purpose, and the new platform better utilizes white space and reserves color to truly highlight the content Blackboard wants to bring front and center. Subtle variations in the “Call-to-Action” button styles were added to make it clearer to the site visitor what the next step is. With the new platform, Blackboard has removed many of the bright yellow buttons and softened their approach and introduced a few more “friendlier” color options to their web palette. The outcome here is that Blackboard.com, the flagship marketing platform looks and feels consistent with Blackboard’s products and services. 

A globally consistent brand experience with localized messaging   

As a global company, Blackboard’s marketing team needs to be able to quickly position their products and services to customers in those markets directly, in their language. Further, Blackboard’s marketing and content strategy varies per market and therefore often by language. Simply translating pages into different languages was not sufficient given it’s often the case that not all products and services are available in all markets, and even when they are they are often positioned differently. A product may be marketed differently in Spain and in Germany while also not being available in Australia, for example, which means we needed a different approach to translation that supported localization. Blackboard’s new Drupal 8 site had to not only provide content in different languages but also content specific to each visitor’s geographic location. 

To support this, we built a Global Site feature in the new Blackboard.com that allows the Blackboard marketing team to spin up and manage new sites in different languages quickly without the need to engage development. At launch, this included close to two dozen sites in around 14 different languages.

We extended Drupal 8 core’s translate functionality to support the variations in language between American English and Queen’s English and Latin American and Castilian Spanish while maintaining flexibility so that content could also be localized for different regions. 

Blackboard’s requirements were complex and caused us to rethink our typical multilingual strategy. Instead of creating a site that supports content in multiple languages, we built a localization platform that takes into account available product offerings as well as language and regional nuance - creating a platform for an organization that is not only multilingual but truly global.

A commitment to web accessibility 

Blackboard and Last Call Media share a commitment to ensuring what we create is fully accessible to all audiences, regardless of ability. To that end, we had accessibility needs in mind from the very beginning. Our cross-functional approach to product development meant that we were able to validate early on that our work would meet WCAG 2.1 minimums, and by engaging users of assistive technology to assist with testing as development progressed, we knew that the release would also be truly usable on day one. 

Goals

We wrote a list of goals for our user testing that included learning about user behavior, whether the site was intuitive to navigate, whether free trials were easy to find, and what users thought about the new design. We worked with the team at Blackboard to define these goals and to ensure we were all on the same page about what we would hope to learn from these interviews. We then constructed our interview questions around meeting these goals, asking users to complete tasks that would ultimately give us the necessary insights for the next phase of work.

Testing setup

On-site at BbWorld, we used Formstack to conduct our user interviews. This gave us an adaptable setup that enabled Blackboard staff to conduct testing right alongside us, even though many of them had never done so before. Speaking directly to users about the site gave Blackboard staff a higher level of empathy with their users than if they had just read a report, giving them deeper insight into how users viewed the site. We also made screen recordings of our interviews, for later reference.

The BbWorld attendees we interviewed consisted of institution technologists, instructors, academic leaders, corporate partners (resellers, ed tech vendors), and trainers, mostly in higher education, as opposed to K-12, government, or business. Most were influencers or decision-makers when it comes to purchasing education software for their institution—a valuable perspective to be sure! In the end, we facilitated almost 70 total interviews over just a couple of days! 

There were a number of initiatives in place to encourage people to test the site. These included push notifications from the BbWorld app, a $15 Starbucks gift card that was given at the end of the testing, and an event-wide “passport” attendees could only complete by visiting our table. Most of the people we spoke to came to us for one of these reasons.

Learning about the old site

The majority of people we spoke to at BbWorld said they had used Blackboard.com before. We were particularly interested to hear from these experienced users, so we could establish a baseline experience using the old site, to later compare their experience using new site. Measuring these experiences against each other would tell us whether or not the restructure and retheme was an improvement. For example, if someone used the site for gathering specific information about Blackboard, did the new site make it easier or harder for them to do that?

Here’s what that baseline experience looked like:

• Half of the people we spoke to said the current Blackboard.com was easy to use, with a quarter each saying it was hard or neutral.
• Most common uses for the site included navigating to Blackboard’s Community site, reviewing the Higher Education section for language on products, or seeking help or support.
• Finding things or navigating the site were listed as the most common difficulty, although some thought it worked well!
• Opinions about the navigation were mostly negative.
• Testers felt that site was clean, but some thought it presented too much information.
• Most people said they access the site by typing the url in their address bar. (A sure sign of an experienced user!)
• Almost universally, people accessed the site from a desktop computer.

Learning about the new site

Moderated user testing is often the first time people outside of your team sees your product. While this can be daunting, it’s important to be open to constructive criticism big and small—after all, that’s the point of user testing! So while we were prepared (as always) for negative feedback, the overall response to the new Blackboard.com was extremely positive. Whew!

While we walked into testing thinking that, visually, the new theme was more of a small facelift than a full redesign, people were enthusiastic about the design of the new site. Before we could even ask about the design, many people immediately stated that they thought it was a big improvement, using words like “clean,” “modern,” and “professional” to describe it.

Many people also liked the new navigation structure. Comments about it included “All the overwhelming links are gone. Now I can digest what the navigation is offering. It’s highlighting the important information,” and “Navigation is simplified and to the point. More intuitive and easy to navigate, it will take a shorter time to get to what I want.”

Despite having a high level of familiarity with Blackboard, two thirds of the people we spoke to said that they learned something new about Blackboard during their brief time on the new site. Blackboard is working to let the public know that they’re more than just an LMS, so we were happy to hear the site is now aiding in that. Blackboard’s recruiting, safety, and social media management services were among the things people most commonly cited having learned about. 

After performing a few tasks on the new site, half of the people we spoke to said the new site was easier to use than the old site, with a quarter each saying it was harder or the same.

But of course there was still room for improvement. Things that people thought could be improved included:

• Many people thought the site wasn’t doing a good job of explaining who Blackboard is and what they do.
• While the new navigation worked well for many people, some expressed confusion over the specifics of what it was presenting. Specifically, they were unsure what was a product and what was a service, and confused about the word “community” being used in two different places to indicate different things.
• Users would often miss the button for free trials, sometimes not seeing it at all until we pointed it out.

Results

The thing that gives our partners the most pause when pulling the trigger on user testing is that you don’t always know what the results will be ahead of time. How can you justify dedicating time and resources to something when you don’t know what you’re going to get? But that’s the point of testing—to find out things you don’t know. We’ve never walked away from testing without valuable insights that went on to inform the rest of the project, and our Blackboard testing was no exception.

One small but impactful result was that we changed the color of the free trial CTA. We made this pivot quickly in the middle of testing, which enabled us to gauge the impact immediately. People started noticing the button more, and thus the issue was resolved immediately — no muss no fuss! It was gratifying to have something so small make an immediate positive impact and we all laughed at how long we chatted about that button color prior to testing! Post-launch, this CTA is used six times more than it was before the redesign, and the page it links to is now the third most viewed on the site, leading more users to this essential content.

Following user testing we did an extensive redesign of the homepage, and the feedback we received stating the site should tell users who Blackboard is and what they do was our guiding light. The new Blackboard homepage is a top to bottom narrative that tells the story of Blackboard starting with a broad overview, then moves into some specifics, and then shows what Blackboard does in action. Post-launch, Blackboard has seen a decrease in the bounce rate of their homepage, meaning more users are engaging with it.

What we learned in user testing also informed the new site navigation. The site structure had been massively rearranged, shifting from being market-based to value-based. The feedback we received about certain parts of the navigation being unclear helped refine the language used. Post-launch, more Blackboard users have been getting to their destination in 0-2 clicks, meaning they’re using the new navigation to find what they’re looking for faster.

The insight that user testing provides can come in the form of reassurance. Since people were enthusiastic about the new site being easy-to-use, we could move forward with the confidence that there were no big missing pieces. Furthermore, since the new theme was so well received, we realized the visual changes provided a larger impact, shifting our perception of it from being a “facelift” to something closer to a redesign.

Goals

The goal of localization for Blackboard’s corporate site was to provide site visitors from around the world with content specific to their region in their region’s language. This means that in addition to displaying content in different languages, we also needed to be able to incorporate regional and dialect-specific (think “color” vs “colour”) versions of content. Also, since not all product offerings are available in every region we needed region-specific navigation as well (to avoid linking to irrelevant content for some users). All of this variation needed to exist between each regional site while allowing some content types to be shared across each region, such as dynamic “resources”, “case studies” and partner content.

Implementation

Location Detection: Not only did we need to provide the ability to display regional content, we also wanted users to be aware of it. In order to do this, we use Acquia’s GeoIP service in order to determine where the user is visiting from. If their country doesn’t match the regional content that they are viewing, we present a modal dialog to show them that we have a section of the site that may be better suited for them. Once they either follow the link or indicate that they are happy where they are we set a cookie so that they don’t continually see the alert. If they leave the section that they have selected, we again alert them but provide the option to stay where they have navigated to.

Regional Sections: In order to provide the regional sections of the site we relied heavily on the “group” module. Each region is a “group” entity, with its own content. We have several “group-level” fields that allow us to define things like language, navigation menus that will appear in each section for each group, region-specific 4xx error pages, and the alias that serves as the beginning of the alias for each page belonging to the group.

Each page node is a part of exactly one group. There may be pages in different groups with similar titles and content, but this model allowed us to have content in the same language and still handle regional colloquialisms, dialects, etc. While the distinct page nodes were distinct for each region, we still had to recognize that there were some types of content had to be reused across regional sections, because creating new educational resource nodes with identical content for each region would not be sustainable. Those content types are allowed to belong to multiple groups. Content listings are built in a way so that they only display content that belongs to the regional section that is currently being viewed.

Multilingual: Possibly the most obvious part of localization is enabling content to be displayed in multiple languages. Drupal’s standard multilingual functionality doesn’t really play nicely with a content model that supports multiple versions (product pages can vary between markets) of content in the same language (think spelling differences between American and British English). In order to accommodate the model Blackboard required, we decided to use Drupal’s language modules, but to leave content translation out of the equation. Instead, we would create different nodes for each language that content was to be displayed in. From the administrative side this approach caused us to lose the “translate” operation for nodes, but in turn gave us a huge amount of flexibility. We were still able to create a site that supports content being entered in 10+ languages (including RTL languages like Arabic), and accommodate localized nuance for each region as well.