Customizing My Welcome Campaign with Local Weather

Bill Miksich
I recently re-joined the team at Customer.io to head a new Professional Services team after about a year away from the company. After spending that year leading the Marketing team at Simple Finance, I had a greater appreciation for the struggles that B2C companies face when trying to keep their lifecycle comms as releva…

How mirroring people’s mental models unleashes superpowers

The most satisfying part of my role as a Product Designer is when we release something that helps our customers become heroes at their jobs. When I help reveal or amplify people’s superpowers, I feel connected to the meaning of my work. There are lots of ways to do that through new features, better reliability, i…

How to come up with design principles for your small design team

At Customer.io, we’ve spent the last year turning our styles and coded components into a full-fledged design system. One of the biggest changes is that our work is now guided by a design direction that includes design principles. What are design principles? Design principles are a set of opinionated, actionabl…

When is it time to level up our design system?

In July 2018, I joined Customer.io as the third Product Designer in a 40-person team. I’d recently left a start up, partly because of the ineffective design practices that bogged down the entire team as we tried to build an app from scratch. There was no system in place — no shared styles of any kind — which made each n…

Starting documentation for our design system

This post is the third in a series to document the challenges and joys of organizing and implementing a design system for Customer.io. We started by auditing our design system, which you can read about here. After the tedious process of auditing our resources, UI, and processes, our next step was to create an organiz…

Auditing our design system

This post is the second in a series to document the challenges and joys of organizing and implementing a design system for Customer.io. If you want to find out why we are building a design system, read the first post here. I joined Customer.io at a time of expansion — over the past year our product team has grown fro…

Customer.io and the Super Awesome Store

‘Push’-ing the limits of inter-disciplinary collaboration “Should designers code?” No. …but successful designers do need to understand how code functions — its constraints, its quirks, its unique capabilities — in order to build experiences which enable users to easily get things done. Similarly, developers…

Creating your first onboarding campaign for new hires

Customer.io
Photo by rachel baskerville on Unsplash Someone new has agreed to join your company, and they’ve signed your offer letter. You’re thrilled! You’re going to spend the next few weeks focusing on making sure their first day is a great one, prepping their onboarding materials, and making sure they’re ready to “hit t…

Customer.io and Zapier Integration! (Finally)

Customer.io
Using Zapier here at Customer.io has helped our tools, and therefore, our teams, talk to each other in ways that help us be more productive. If you’ve ever cracked the nut on a big time saver, you know how good it feels — we couldn’t keep all those good feels to ourselves anymore. We’re excited to share our integration …

Hack project to full-feature: Improving Customer.io email Layouts

Ivana McConnell
Recently at Customer.io, we released a Layout Starters feature. What began as a hack project at our recent Iceland retreat grew into a full-fledged piece of product work, along with a new suite of documentation. We’re pretty proud of it and wanted to share! This post digs into both UX process and front-end, and comes…
Join our mailing list for updates on our How We Work content and more!