Airship is a customer messaging platform. Marketers use it to plan, build, send, and measure messages across many channels. As Staff Product Designer I worked on it inside the product team. I shipped new features and reworked old ones across the busy, packed screens that make a complex B2B tool feel manageable.
The work went two ways. I built features from zero (the campaign calendar, guided creation, the asset library) and I redesigned old screens (the messages dashboard, analytics) to make them clearer. One good-looking screen was never the tricky part. The tricky part was keeping everything clear, consistent, and predictable across very different views.
- Role
- Staff Product Designer
- Domain
- B2B engagement platform
- Way of working
- Embedded in the product team
- Scope
- New features + redesigns
Designing for density, not for the demo
A platform like this lives or dies on its busiest screens. Heavy users run dozens of campaigns across channels at once. So the design job is to keep all that readable. The layout has to stay clear when the screen is full of data, the states have to be predictable, and the style has to feel the same across very different screens.
- Make busy calendars and tables easy to scan instead of overwhelming.
- Keep status, channel, and state obvious at a glance.
- Hold one consistent style across planning, assets, messaging, and analytics.
Closer to the customer than the brief
Not every task came top-down from product. This is a B2B segment, so the people who actually run these campaigns are reachable. I went to them directly. I put demos and clickable prototypes in front of real customers and users, gathered their feedback first-hand, then refined the work back inside the team. I could start those conversations myself rather than wait to be asked, and use each demo to get extra feedback from B2B customers before the engineers started building.
To keep that loop fast, I built the prototypes with AI tools. A flow becomes real and interactive in a few hours, so the feedback lands on the actual thing rather than a static mock.
Campaign calendar
This is the planning surface. It is a month, week, or day calendar where every message is colour-coded by workflow. Overflow (ā+N moreā) and filtering keep a packed month readable.
Messages dashboard
This is the home for everything that ships. Automations, one-off messages, in-app, and A/B tests all sit in one table. Status, channels, audience, and delivery read at a glance. Filters and tabs (Ongoing, Scheduled, Need Review, Draftsā¦) cut the list down.
Guided creation
Creation starts with what you want to send. Pick a message, sequence, or scene, then a template grouped by goal, like Onboarding, Activation, Loyalty, Winback, or Promotions. No more blank page.
Campaign assets
A searchable, tagged asset library for each campaign. It has grid and list views, keyword tags, and asset-type filters, so teams reuse the right creative instead of re-uploading it.
Analytics overview
Performance at a glance. KPI cards with trends, a chart comparing people who got the campaign with those who didn't, a channel breakdown, and engagement by platform. The numbers a marketer checks first are shown first.
What it adds up to
New and reworked features that read as one product. Planning, messaging, assets, and analytics, designed in-team with PMs and engineers. The product stays clear even when it's full, and not only in the demo.