Case study · Shoniz
Ding
A modern, stable and scalable internal communication platform
- Role
- Product Designer, owned the project end to end
- Context
- Shoniz
- Tools
- CommunicationEnd to endMobile
01
Context
The problem
Ding brings internal communication into one reliable platform. It is developed and published on the Bazaar marketplace.
What was broken
Internal communication was scattered across multiple disconnected tools, which made conversations hard to follow, files easy to lose and collaboration slower than it needed to be.
02
Approach
How I got there
01
Field research and talks with the stakeholders to understand the real work, desk research on similar products and best practices, and business meetings to agree on the problem and find the solution. I did the full product-design scope: research, solution finding and design.
02
Competitive analysis across Microsoft Teams, Slack, Pumble, Ryver, Google Chat, Zoho Cliq, Twist, Teamwork Chat and Flock, plus relevant apps on Bazaar and Google Play.
03
Mapped the UX patterns, trust signals and messaging flows modern users expect, and decided what fits the teams best.
04
Structured the core flows and designed the full experience around clarity and ease of use.
03
Thinking
Key decisions
I decided to
One platform for chat, channels, files and calls
Because
Communication was scattered across disconnected tools, so conversations were hard to follow and files easy to lose.
04
Impact
Results
- A single, unified space where conversations, files and calls live together.
- Reduced friction, kept teams aligned and made everyday collaboration noticeably simpler.
- Impact was not measured in numbers for this project, so these results are qualitative.
Why so few screens? Most of this work is under NDA, so I can only share a small part of it. I am happy to walk through the rest in a conversation.
The craft