Year One Retrospective

Chris Jeong
Nov 30, 2018 · 4 min read

During my first year at Liferay, I had the pleasure of contributing to taking Analytics Cloud from an idea to reality.

During this period, we’ve had anywhere between 3 to 8 designers at various design stages attending brainstorming sessions, providing countless comments over Invision and Figma, and at times flying thousands of miles just to be in the same room together. We did all of this in the name of taking an abstract idea to a concrete product.

But as our design team starts to scale in size and across borders, I find asking myself, how can we be more effective and impactful? These are my reflections from this past year.

Image for post
Image for post
Photo by Ross Findon on Unsplash

Have a guiding star

The agile manifesto prescribes every effective agile team to embrace change, but only when it provides meaningful customer value.

Image for post
Image for post
Photo by Caleb Woods on Unsplash

When I look back to roadmap from the inception of this project and compare it to where we are now, the initial requirements seem like a world away. The features and functions that were initially laid out have been stripped to the fundamentals of the product and we are happy with where it stands now.

The idea is that we’ll provide the high value parts and let our customers guide the direction to take. This means, going forward, we need to be more proactive in finding our customer’s voice with research and support.

Avoid designing by committee, at all cost.

Early in the design process, we engaged in divergent brainstorming and ideation sessions which generated in tons of great ideas, but weren’t prepared to execute those ideas.

Image for post
Image for post
Photo by Nicolas Gras on Unsplash

Divergent thinking challenged us to explore many possible product directions by leveraging:

  • Unique viewpoints
  • Varying levels of understanding
  • Disparate teams with differing goals

This was the easy part.

However, when the designers got together to build on these explorations, I found we lacked a process for converging and distributing the work. This invariably resulted in design by committee, which was a huge drain on resources and resulted in a lot of overlap of work.

Eventually we were able to reorganize. We can Slack all day, but nothing beats being in the same room together. A short 20 hour flight to Brazil and a few discussions later, we were able to resolve these incongruences almost immediately.

The lesson here for us was that freeform creative exercises are an invaluable part of the design process, but they are only as effective as the execution strategy. Going forward after each exercise we must determine:

  • An agreed set of requirements
  • Explicit ownership to the different parts of the product’s design
  • Setting design goals and milestones — with some expectation of change

Design-Ops

UX Design has come a long way from proving the ROI of a great user experience and discussing designer/developer collaboration.

Image for post
Image for post
Photo by Matt Artz on Unsplash

Design-ops has been a hot topic sparking conversation within our organization over the past year. As our department enters a new phase of maturity, we are looking beyond the design tools:

  • Design processes are a constant work in progress, learn to accept that and build on what works
  • Design Systems help us work faster and focus on the problems that matter
  • Digital Asset Management, just do it…
  • User research MUST be socialized, or it’s useless
  • A centralized database for User Research “nuggets” — currently being developed with Juan Hidalgo Reina on Airtable
  • Collaboration during designing (tools like Figma help)
  • Don’t hide behind a screen — talk to EVERYONE

Product Management

When product and design goals align — the focus naturally turns towards the users

Image for post
Image for post
Photo by Samuel Zeller on Unsplash

I look to our product managers to provide me a with a strong vision and strategy, so that I can synthesize that vision in to a design customers will find valuable. However, that’s not to say designers don’t have a say in how to steer the ship. The designer/product relationship share tons of overlap in resources and goals, which make us designers the perfect partners to our product managers. (Tom Hagen/Don Corleone anyone?)

  • Sit in on customer calls to get context in to the decision making for the product vision and strategy
  • Sharing user research and competitive analysis, allows us to refer back to a single reference point to anchor our positions
  • Surface discrepancies of customer needs and product strategy to spark discussion
  • Engage in high level design activities such as customer journey mapping and concept wireframes together, for alignment

Conclusion

2018 was a big year for us here at Liferay. We went from being a single product company to having 3 new products to go along with our new and improved portal offering. With the lessons from a whole year of working together, I’m excited how our design team and product will evolve in the coming year.

Originally posted by Chris Jeong at liferay.design/articles on November 29, 2018.

Liferay Design

What's happening in Liferay Design?

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store