Productboard AI is now generally available!
Building a design system without knowing how it is used can be very tricky, and even the simplest of questions can be hard to answer. Do you know how often your components are used? Can you remove deprecated components from the code? What is the adoption of your design system?
It was in the spring of 2018 when I first interviewed for the position of a product designer at a local startup — you guessed it, Productboard.
In part one, I provided an introduction to our design ethos and team set-up here at Productboard. For part two, I’ll discuss how we work, focussing on the important matters of collaboration and feedback.
As we continue to grow at a rapid pace, we’re always on the lookout for talented new designers to join our team. We interview a lot of people in the process. And those people ask a lot of great questions. In this series of articles, I’ll answer some of the most frequently asked questions we get asked.
In this series of articles, I answer some of the most common questions we get asked by design candidates during the interview process. The aim is to provide as much clarity as possible, giving future candidates all the information they need to approach their Productboard journey with confidence.
At Productboard, we’re adopting a service-oriented architecture for two reasons — to enable faster decision-making in empowered teams and allow us to staff quicker by adding two more stacks into the mix we develop in.
One interesting thing I have observed over time is that open-source solutions tend to struggle with bigger code bases. That’s when custom tooling comes into play — or not necessarily. The truth lies somewhere in the middle.
Web Can I use is an indispensable part of every web developer today. Can I use provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.
ur Design team grew three-fold last year, from four to twelve, including our first dedicated UX Researcher. This year, the plan is to expand the team further across the EU and the US. 📈
A year and a half ago, I took the opportunity to build the Frontend Platform team that I’m still leading today. While I did this for many reasons, one of them was particularly striking: To empower product teams to make high-impact changes, enable and support innovation, and share our learning across the frontend community.
Designing for engagement is an important ingredient in creating great companies and great products. We see companies like Airbnb and Nike, where long-term, brand-led efforts have led to customer loyalty.
In the first article in our People of productboard series, we caught up with Julia Rosich, one of the latest additions to our growing design team and our first fully remote designer.