paul.hanaoka.co

Fostering a culture of growth and design excellence

Problem

Hiring good designers for an enterprise software company is a perennial challenge, especially if your corporate website has all of the constraints of the typical corporate website.

Once you hire a good designer — how do you onboard, grow, and retain them?

Role

As one of the Design Managers on the team, I contributed to the content strategy and design. In my spare time, I was the lead developer for the site, contributing over 250k lines of code.

Contributions

  • Content Strategy
  • Information Architecture
  • Wireframing
  • Interaction Design
  • Prototyping
  • Usability Testing
  • Quality Assurance
  • Frontend Development
  • JSX / SCSS / MDX

Impact

Reduced Time to Hire300

From Months to Weeks

Designer Retention240

Significantly over industry average

Designers Hired40

From 2018 to 2023

Solution

Creating a home on the web for our small, yet growing, design team was one way to compete with cool startups who were able to lure top talent.

On one hand, yes — this was just a few websites — but it became so much more, a tool and place for us to learn and grow together.

Along the way, I learned a ton about management, engineering, marketing, and how hard it is to design for designers.

A screenshot of the commit history

The Liferay.Design Ecosystem

What initially started as a landing page for our first Design meetup grew to a monorepo that held our entire DesignOps library, including our Department Handbook and Design System documentation.

I learned how to use Firebase Authentication and created an "internal only" brand guideline section of the site.

I also connected to external tools and services like Cloudflare to manage domains and even a MailChimp integration to automatically generate a newsletter archive.

Initially launched as a basic react app, I rebuilt it in Gatsby using Theme UI and MDX for flexibility and portability.
A major milestone was launching profiles for each designer — creating your profile was one of your first onboarding tasks when you joined the team.
Writing stuff down help teams learn and grow together efficiently. I started the Handbook as a side project in Google Docs, eventually creating a dedicated site within the site for it.
One of the engineering teams had built an MVP site for our Design System, one of my earliest contributitions to Lexicon was upgrading it to a more complete documentation site and bringing it into our repo.
A pain point our Marketing Designers had was constantly having to share brand assets with a variety of teams. I helped them by creating a private brand guide they could update and share with internal teams and vendors.

Hire & Onboard

A huge challenge we faced was awareness. Despite being in business for over 10 years with offices in major cities across the globe, almost no one in the design community knew about Liferay.

To address this, Design Managers in each region (I was the lead Manager in North America) hosted events, wrote articles, and encouraged the team to publish work and writing as a way to share knowledge and generate traffic to the site.

When we had built a good rythm of contents and events, I started a monthly newsletter which grew to 170 subscribers after a year. While not amazing numbers, it definitely helped legitimize our team and even though people still didn’t really know about us, the site and all the content helped Designers immediately feel like they wanted to be part of the team.

screenshot of the article page
In its heyday, we were publishing two articles a month.
screenshot of the events page
In cities like Madrid, our office was centrally located and events were packed. Our site served as a place to get RSVPs and share recaps.
screenshot of the newsletter archive
Connecting the MailChimp API to our site allowed us to have an automated newsletter archive.
screenshot of a job ad
Liferay used Jobvite and if you’ve used it before, you’ll understand why we made a dedicated section on our site to share nice job ads.
screenshot of our onboarding handbook page
This was the start of our onboarding process, the repo helped our team consolidate a variety of different onboardings into a more cohesive, globally refined process.
screenshot of the team page
One of the first onboarding tasks was adding yourself to the team page.

Grow & Get Better

Liferay’s designer retention was in-line with the industry average of 1-2 years. While this is fine if you’re a large company and can attract talent easily, this rate made it exceptionally challenging to improve the design maturity of our company.

One initiative that I contributed heavily to was creating career paths for Designers, including tool that I forked from the Medium engineering team, adapted to our needs (including connecting to a Google doc as a content source) and published as a standalone site to help managers level and grow their teams.

Along with many other efforts led by Juan Hidalgo, helped to create a culture of learning and growth that retained Designers for 2 to 3x longer than industry average.

Screenshot of the career paths page
path.liferay.design was a standalone tool I made for designers and managers to be globally aligned on our career levels.
a screenshot of Best Practices articles we wrote
I organized the whole department to write a series of Best Practice articles
As part of our annual report (which is another story) I created a page to showcase promotions, to celebrate the team’s growth.

By the Numbers

Newsletter Subscribers170

Significantly over industry average

Weekly Visitors1K+

We were able to generate traffic without any ad spend

Pageviews1M+

More than 250k pageviews annually

In Retrospect

Was this a good idea?

Absolutely, yes. The team loved being able to have one place to go and find almost anything they needed.

It also served a great tool teach Designers technical concepts, tools, and workflows. I trained over 20 Designers, who had never used Git before, how to clone a repo, install dependencies, make changes in code, and submit pull requests.

Would I do it again?

"It depends."

There are many factors to consider. At the time I started this project, I didn’t realize how much of an investment it would be. While it was a great way to learn a lot, and especially helped me level-up as a react developer, I would thoroughly consider the goals, opportunity costs, alternatives, and long-term impacts before I would undertake something like this again.

I loved adding fun, yet strategic, details like random headshots with articles to help prevent bounces.
Next Project
Driving revenue by improving quality across an enterprise platform How focusing on design quality can impact a business
Enterprise
Platform

Driving revenue by improving quality across an enterprise platformHow focusing on design quality can impact a business