Aleksandr Mihhailovski

Seamm · 2023

Stories Editor

How I eliminated a 2-day content publishing bottleneck.

Overview

Designed a no-code story editor that gave marketing full autonomy over Instagram-like content creation, reducing creation time from 24-48 hours to 5 minutes.

My role

Product Designer — UX, UI, design system

Team

Seamm product team

  • PM
  • Design Lead
  • 2 Engineers
  • Product designer (Me 👋)
Impact
  • 24-48h → 5 min creation time
  • 10× campaign velocity
Hero: Stories Editor interface
Story creation time
24-48h → 5 min
Campaign velocity
10×
Engineering time freed
~20 h/week
Before
Marketing
Slack message
Dev team codes story
Wait 24-48h
Publish
After
Marketing
Visual Editor
Instant Preview
Publish (5 min)
01 · Context

Why we started

Seamm’s marketing team needed to create Stories — Instagram-like vertical content — to showcase products and drive engagement. Every single story required a Slack message to engineering, manual asset preparation, and developer intervention to code and publish.

Marketing couldn’t see how a story would look on a user’s device before publishing. Nothing prevented wrong colors, wrong fonts, or text overflow. And every change — even a typo fix — required an engineer.

The goal
Design a no-code editor that empowers marketing to create, preview, and publish brand-safe stories independently — transforming a multi-day engineering task into a 5-minute self-service workflow.
Key insight
Content creation sat at the same expensive intersection as push notifications: marketing couldn’t publish without engineering, and engineering had higher-priority work.
02 · Preview

How to kill ‘blind publishing’?

The core problem was what I call ‘blind publishing’ — marketing had zero visual feedback before content went live. They were mentally simulating what the story would look like, then hoping for the best.

The solution was a real-time mobile preview. As the user types, the left panel shows exactly how the story will appear on a user’s device. Not an approximation — the actual app dimensions and typography.

Screenshot: Stories editor with live mobile preview
The mobile preview uses actual app dimensions and typography — what you type is what users see.
Design decision
I considered a separate Preview step (Edit → Save → Preview → Publish), but chose live preview because it reduces friction, enables rapid iteration (3 variants in 5 minutes), and eliminates approval anxiety. Trade-off: more complex frontend state management, but the UX benefit justified the cost.
03 · Constraints

How to prevent brand-breaking  mistakes?

Before the editor, there were multiple incidents of wrong colors, broken links, and text overflow going live. To prevent this, CTA buttons use a color picker locked to the brand palette — only approved colors are selectable. Character counters prevent overflow. Link destinations are validated.

Screenshot: Brand-locked color picker and validation
Template constraints reduced brand inconsistency errors by ~90%.
Design decision
I considered inline editing — clicking directly on the preview. But a dedicated side panel shows all options at once (character limits, link types, color constraints) without hunting. The small mobile preview makes inline clicking error-prone. Trade-off: less spatial directness, but dramatically fewer errors.
04 · Autonomy

Why templates, not a free-form canvas?

This was the most important design decision. I considered a Canva-style free-form editor. But templates guarantee mobile optimization, prevent overlapping or off-screen content, and let users focus on content instead of layout.

Marketing needed speed and consistency, not design experimentation. The template system became the most-valued feature — marketing wanted confidence over flexibility.

Screenshot: Story management dashboard
Marketing now manages all stories in one place with complete autonomy.
Key insight
Reducing options turned out to be more empowering than adding them. Templates eliminated an entire category of anxiety — ‘did I break the layout?’
05 · Results

Results

100% marketing autonomy

Zero Slack messages to engineering for story updates. The self-service system handled everything from creation to publishing.

10× campaign velocity

Story creation dropped from 24-48 hours to 5 minutes. Marketing launched 3-5 stories per week, up from 1-2 per month.

~20 hours/week freed

Engineering time redirected from repetitive story tasks to core product features.

Key insight
The real win wasn’t just speed. It was giving marketing complete ownership of their channel while guaranteeing brand safety through design constraints.
06 · Lessons

What I learned

01

10× velocity comes from removing people, not adding tools.

The bottleneck wasn't slow software. It was a Slack message to an engineer who had other priorities. The editor didn't speed up the process — it removed a step entirely.

02

Preview kills anxiety.

Every tool that shows 'what you'll get' before you commit reduces fear of mistakes.

03

Constraints are a feature, not a limitation.

Brand-locked colors and template boundaries initially felt restrictive. Turns out, removing decisions that don't matter lets people focus on decisions that do.