MEDIA ECOSYSTEM / PRODUCT DESIGN
FOMecosystem
A portfolio of media products, internal tools, and editorial platforms needed one manageable logic without flattening every project into the same visual voice.
- Top-3
- sociological research company in Russia
- 5+
- products inside the ecosystem
- 10+
- key product stakeholders
- Media
- editorial ecosystem
CONTEXT
Not one website. A media portfolio.
- 01Many stakeholders10+ product owners, internal teams, external clients, and different decision makers.
- 02Different expectationsEach group had its own standard for quality, speed, tone, and outcome.
- 03Different audiencesThe portfolio ranged from field research to crowdsourcing platforms, media portals, and internal products.
- 04Uniform design was not the answerThe products had to stay distinct, but become easier to manage as one ecosystem.
APPROACH
The focus moved from one visual system to shared product logic.
DESIGN PROOF
Media portals, editorial screens, states, cards, and visual rules
The long images are shown in full because the case is about product depth: navigation, article logic, editorial formats, states, and the system behind recurring media pages.
Editorial product screens
The health media direction had to work as a repeatable product environment: navigation, article pages, editorial hierarchy, and content patterns.


Special project page
This is a separate special project page inside the ecosystem: a public healthcare project with event content, speakers, partners, news, and a press center.

System rules and reusable states
The work included operational details that make a media ecosystem usable: subscription states, color rules, announcement cards, and content-card behavior.



MY ROLE
I turned a scattered portfolio into a design logic the team could use.
My work sat between product thinking, interface structure, stakeholder alignment, and visual quality. The goal was not to make every project identical, but to make the portfolio easier to evolve.
- 01Mapped the product landscapeI worked through the portfolio, stakeholders, audiences, and product types to understand where the ecosystem needed shared rules and where it needed flexibility.
- 02Translated requests into principlesDifferent wishes and requirements were turned into design principles, decision frames, and repeatable interface logic.
- 03Designed editorial structuresI shaped navigation, article logic, special project pages, announcement cards, subscription states, and reusable media patterns.
- 04Aligned many decision makersThe work required holding quality and clarity while several product owners, teams, and clients influenced the outcome.
- 05Protected the portfolio logicThe final system gave products room to differ visually while preserving consistency, predictability, and a shared standard of interface quality.
OUTPUT
What became stronger
- 01Shared design principlesThe products could remain visually different while following one quality and decision logic.
- 02Editorial ecosystemMedia portals, articles, project pages, cards, and states were treated as parts of one product system.
- 03Stakeholder clarityRequirements became easier to discuss, compare, and turn into decisions.
- 04Higher product trustConsistency and UI quality increased together with product activity and trust in the platform.
Ready to start?
If you have questions about this case or want to bring your own project, write to me on Telegram.
Write on Telegram