Aristotle International · Program 360 · 2025
Program
360
A mass email and SMS marketing platform for PAC members and political workers — designed solo, built on the Aristotle Design System.
Organisation
Aristotle International
Role
Solo Product Designer
Design System
Aristotle Design System
Deliverable
Email & SMS Marketing Tool
An Aristotle product. A solo design effort.
Program 360 is an Aristotle International product — a purpose-built mass communication platform for PAC members and political workers to send targeted email and SMS campaigns at scale.
As the sole designer on the project, I owned the entire product design process from initial scoping through to final delivery. There was no design team to hand off to, no parallel track to cross-reference — just a clear product brief, a set of user needs, and the design system I had already built for Aristotle's product ecosystem.
That design system became the backbone of Program 360. Every component, every pattern, every interaction was drawn from the Aristotle Design System — ensuring that Program 360 felt native to the broader product family from day one, rather than a standalone tool bolted onto the platform.
The goal was to make mass political communication feel manageable. Campaign managers needed to draft, schedule, and send to thousands of PAC members without the overhead of a general-purpose marketing platform. The design had to be opinionated enough to guide users through a complex workflow, and familiar enough that they never felt lost.
Mass Email & SMS
Bulk communication to thousands of PAC members and political contacts across email and SMS channels.
Audience Segmentation
Filter and target recipients by role, region, committee, and custom criteria.
Scheduled Sends
Queue campaigns for precise delivery without manual intervention.
Design System–led
Every screen built on the Aristotle Design System — consistent, scalable, and on-brand.
Three states, one clear picture.
The campaign list is the operational heartbeat of Program 360. Users needed to see exactly where every campaign stood — Draft, Scheduled, or Sent — and switch between a personal view and a team-wide view without losing context.
Draft Campaigns
Campaigns in progress. Users can filter between all drafts in the system and only their own, keeping large teams from drowning in each other's work.
Scheduled Campaigns
Campaigns queued for delivery. The same All / My filter pattern keeps the view consistent and predictable regardless of which tab the user is on.
Sent Campaigns
Completed sends. The archive of what went out, when, and to whom — a reference point for performance review and future campaign planning.
Card & Grid Views
Beyond the default list, users can switch to card or grid layouts — giving teams a visual overview of campaign thumbnails and metadata at a glance. These view modes were designed as part of the Aristotle Design System's flexible data-display patterns.
Write it. Preview it. Send it.
The email composition flow needed to feel like a focused writing environment — not a marketing platform with a hundred options. The goal was to keep the user's attention on the message, not the tool.
The preview panel was a deliberate design decision. Political emails often carry strict formatting requirements — headers, disclaimers, unsubscribe links. A live rendered preview before sending reduced the risk of costly formatting errors going out to thousands of recipients. The composition interface follows the Aristotle Design System's form and editor patterns, keeping the experience consistent with the rest of the platform.
The right message to the right people.
Audience selection is where the complexity of political communication becomes most visible. PAC members, committee staff, field workers, and donors all have different communication needs. The audience module needed to make segmentation feel manageable, not overwhelming.
Role-based filtering
Segment by PAC member type, committee role, or organisational affiliation.
Multi-criteria selection
Stack filters to build precise audience lists without writing a query.
Reusable segments
Save audience configurations for recurring campaign types.
Precision timing for political sends.
Political communications are time-sensitive. A message sent at the wrong moment can undercut its own impact. The scheduling interface needed to make precise timing feel easy — not like configuring a cron job.
The scheduling step sits at the end of the campaign creation flow — after the message is written and the audience is set. This sequencing was intentional: users commit to the content and recipients before they commit to the timing, reducing the chance of scheduling an incomplete campaign. The date and time picker reuses the Aristotle Design System's input components, keeping the interaction familiar across the platform.
The infrastructure behind every send.
Before a campaign can go out, the system needs to know who it's coming from. Sender profiles, campaign configuration, and the add-campaign flow form the operational backbone of Program 360.
Sender Profile Setup
Adding a Sender Profile
Campaign Creation & Editing
What happened after the send.
Sending is only half the story. Campaign managers needed to understand what happened after — who opened, who clicked, what bounced. The performance module closes the loop between intent and outcome.
Delivery Rate
Track how many messages successfully reached their recipients.
Open & Click Rate
Measure engagement quality beyond raw delivery numbers.
Campaign Comparison
Benchmark performance across multiple sends to refine future strategy.
What it means to own a product solo.
Program 360 is one of the most end-to-end design challenges I've taken on within Aristotle. No design partner to pressure-test ideas with, no parallel track to cross-reference — just a product brief, a set of user needs, and the design system I had already built.
Being the only designer on a product forces a discipline that collaborative environments sometimes dilute. Every pattern had to earn its place — because I'd be the one maintaining it. Every interaction had to be self-evident — because there was no one to explain it to users. Every screen had to work in isolation and as part of a larger flow.
The Aristotle Design System made that possible. Having a shared component library and established interaction patterns meant I could move quickly without sacrificing consistency. Program 360 didn't need its own design language — it needed to feel like a natural extension of the Aristotle platform, and the design system made that the default rather than the exception.
The biggest design challenge wasn't any single screen. It was the consistency of the mental model across the entire product. When a user moves from drafting a campaign to selecting an audience to scheduling a send, the transitions need to feel inevitable — not like switching between three different tools.
Design system as foundation
Building on the Aristotle Design System meant Program 360 felt native to the platform from day one — no bespoke patterns, no inconsistencies to resolve later.
Solo ownership sharpens decisions
Without a team to defer to, every design decision had to be defensible on its own merits. That constraint produced cleaner, more intentional work.
The send is not the end
Building the performance module reinforced that the product's value isn't in sending — it's in learning. The analytics close the loop that makes the next campaign better.