FROM CREATING MESSAGES TO MANAGING COMMUNICATION AS A SYSTEM.
A 0→1 internal communication platform concept for the teams responsible for communication across an organization.
Communication isn't one message — it's a series of decisions.
For communication teams, every message means a series of decisions: who sends it, who should receive it, which channels it needs to reach recipients through, whether it requires approval, and when it should go live.
The task within the challenge was to explore how all of these activities could be combined into one coherent product experience — instead of treating them as separate, scattered tasks.
I worked on this project solo, from 0 to 1, as part of Żabka Future — AI Supercharge Challenge, taking full ownership of the product concept and design direction end-to-end.
Problem
One question that set the entire direction.
How might we make internal communication easier to create, control and distribute.
The starting point was a simple need: communication teams needed one central place to manage internal communication. Instead of treating publishing as a single action, I focused on the decisions that surround every message.
That's where the opportunity emerged to connect the full message lifecycle — shown above as Create → Review → Approve → Target → Schedule → Distribute.
Before designing the editor, I mapped what surrounds it. I started by reviewing competitive and related products to understand how communication workflows are typically built, and where each part of the experience usually sits within a typical product.
Who is communicating?
Who should receive it?
Who needs to approve it?
Where should it appear?
When should it be published?
That led me to a product model where communication is managed as one connected system — not a sequence of separate tools.
Solution
One system, four connected jobs.
I worked on this project solo, from 0 to 1, covering the full design scope — product concept and naming, competitive research, information architecture, UX/UI, design system, AI interaction design, content, and the final prototype. I used stakeholder feedback to refine the direction and priorities.
Key Decisions
Instead of walking through screen after screen, here are four design decisions along with the problem each one solved and the reasoning behind it.
Reflection
LCM - Complex product, simple message.
Large organizations run on software. Hundreds of licenses across different vendors, teams, and devices — each with its own cost, expiry date, compliance requirement, and renewal window. Most companies don't have a single place to see all of this. They overpay for unused licenses, miss renewals, and risk compliance violations without knowing it. APN Promis built LCM — License Compliance Manager — to solve exactly that. A SAM-as-a-Service tool that centralizes all license data in one place. The product was strong. The problem was it had no page that could explain it to the people who approve budgets.