Case Studies Revamp


Company projects were spread across the website in a disorganized way, making them challenging find. Once found, the information would be displayed in an inconsistently between projects and many times incomplete.

A person wearing glasses
				Description automatically generated with medium confidence

‘I grasp Hitachi Energy’s long history, but it is difficult to find projects similar to mine which they have worked on in the past or a currently working on’


Needs to actively search for projects across product pages, news and reports

A person with a beard
				Description automatically generated with medium confidence

‘It is hard to display our experience and know-how if we rely on constantly updating internal slides and regularly asking Business Units about information on their latest projects’


Repeatedly requests updated projects’ information when presenting to prospects

Back To Top

Proposal & Process

The proposal was to standardize projects by structuring them as Case Studies and cataloging them through a centralized tool. This tool would empower users to easily sort and filter by predefined categories.

It was necessary to go through the following steps:

  1. Collect throughout the website all existing pages that meet the Case Study criteria
  2. Clean-up and sort through the collection
  3. Brainstorm, define and agree on a tagging/categories system that would work within all Business Units
  4. Tag each Case Study individually matching the desired tagging system
  5. Analyze existing Case Studies to find patterns in information that should be displayed
  6. Go through the template creation process with stakeholders
  7. Migrate existing pages into Case Studies
  8. Design, develop and test the filter and sorting component
  9. elease the new component and include in multiple product pages

Step 3,4,5 and 6 were interconnected and required to be re-runed in several iterations.


The initiative provided 4 deliverables:

The most impactful was the Case Study Selector, a component that displays descriptions and links to all Case Studies. It allows users to filter between 7 possible categories. The component can be configured in the backend to provide the most relevant filters on each page. The second iteration allowed to showcase a limited amount on Case Studies based on criteria set on the backend.

A new Case Study Template and writing guidelines to use it. Existing projects’ references needed to be re-written to fit a Case Study Template. Editors were led by the Case Studies guidelines which showed description to each section, example texts, and best practices.

A centralized backend system. All Case Studies are now stored in a simplified folder structure in the Content Management System. This makes content updating easier since editors can filter and browse through all pages in the backend without needing to traverse through the entire website folder structure.

A tagging system. A uniform set of 120+ tags from 5 categories (Offering, Markets, Country, Specific Products, Voltage) that is suitable for the complex products and services range of all Business Units.


The new Case Study Selector brought momentum to the importance of showcasing the company’s projects to customers. This started a culture shift within the product marketing teams so that new Case Studies are published every week and the content quality of older Case Studies was improved.

The number of monthly visits for Case Study pages compared to their corresponding original pages doubled or tripled. From a low average 400 monthly views up to 1500, and in many cases grew from 0 to 1,000 monthly visits.

The Sales team benefited from receiving updated information about the company’s projects using the website as an initial source of truth. This also allowed for more transparency when sharing information to customers since most of it is now publicly available.

Products, News and Events pages can now be easily connected with relevant Case Studies by having a Case Study Selector limited their topic in a section of the page. This allows for better storytelling and adding context to the page’s content.


This initiative faced many difficulties among them:


This initiative required me to wear two hats:

Project Manager

User Experience Consultant


From this project I got three main takeaways:

  1. A great product is the one that can start a culture adjustment in an organization. Before the Case Study Selector, content on existing projects were peripheral and eclipsed by new products and services. After the Case Studies became easier to understand, find, and update: they gained meaning.
  2. Working across departments that are siloed can become a never-ending job if you don’t keep an eye on time. It is important to set expectations and deadlines to avoid the project from extending itself.
Next Case Study: Page Templates