Greator

Brand Elements, Design Systems, and File Structuring for a Coaching Platform

Duration

6 months

Made with

Greator

Stakeholder

Greator

Industry

Coaching

In fast-growing products, clarity is often the first thing to break. This project shows how UX and interface decisions helped a growing education platform scale without transferring complexity to users.

Greator

Brand Elements, Design Systems, and File Structuring for a Coaching Platform

Duration

6 months

Made with

Greator

Stakeholder

Greator

Industry

Coaching

In fast-growing products, clarity is often the first thing to break. This project shows how UX and interface decisions helped a growing education platform scale without transferring complexity to users.

Greator

Brand Elements, Design Systems, and File Structuring for a Coaching Platform

Duration

6 months

Made with

Greator

Stakeholder

Greator

Industry

Coaching

In fast-growing products, clarity is often the first thing to break. This project shows how UX and interface decisions helped a growing education platform scale without transferring complexity to users.

Context

Greator is a digital platform focused on education and professional growth, offering a constantly expanding mix of content, events, and digital products. The main challenge wasn’t missing features, but speed of growth. New initiatives were introduced frequently, increasing complexity and overlap across the experience. The risk was losing clarity while the business accelerated.

The real problem

The core issue was experience fragmentation. Individual parts of the product worked in isolation, but users struggled to orient themselves across offers, content, and actions. UX decisions were often made locally, improving single touchpoints without addressing the overall structure. In a growth-driven product, this created friction exactly where clarity mattered most.

My Role

I worked as a Senior UI / Product Designer, collaborating with product teams and business stakeholders.

My focus was on shaping the overall experience, defining a clearer structure, and aligning user needs with business goals through coherent UX and interface decisions.


Context

Greator is a digital platform focused on education and professional growth, offering a constantly expanding mix of content, events, and digital products. The main challenge wasn’t missing features, but speed of growth. New initiatives were introduced frequently, increasing complexity and overlap across the experience. The risk was losing clarity while the business accelerated.

The real problem

The core issue was experience fragmentation. Individual parts of the product worked in isolation, but users struggled to orient themselves across offers, content, and actions. UX decisions were often made locally, improving single touchpoints without addressing the overall structure. In a growth-driven product, this created friction exactly where clarity mattered most.

My Role

I worked as a Senior UI / Product Designer, collaborating with product teams and business stakeholders.

My focus was on shaping the overall experience, defining a clearer structure, and aligning user needs with business goals through coherent UX and interface decisions.


Context

Greator is a digital platform focused on education and professional growth, offering a constantly expanding mix of content, events, and digital products. The main challenge wasn’t missing features, but speed of growth. New initiatives were introduced frequently, increasing complexity and overlap across the experience. The risk was losing clarity while the business accelerated.

The real problem

The core issue was experience fragmentation. Individual parts of the product worked in isolation, but users struggled to orient themselves across offers, content, and actions. UX decisions were often made locally, improving single touchpoints without addressing the overall structure. In a growth-driven product, this created friction exactly where clarity mattered most.

My Role

I worked as a Senior UI / Product Designer, collaborating with product teams and business stakeholders.

My focus was on shaping the overall experience, defining a clearer structure, and aligning user needs with business goals through coherent UX and interface decisions.


Designing for clarity and orientation

The work focused on reducing cognitive load and simplifying user decision-making. Information architecture was restructured to clarify main paths, distinguish content from offers, and highlight priority actions. Rather than optimizing individual screens, the effort established consistent UX rules that could support product evolution without introducing new ambiguity at every iteration. The goal wasnt to make everything simple, but to make it clear what to do, when, and why.

UI Toolkit and Pattern Libraries

The next step was creating the UI toolkit and pattern libraries. These components included core elements like typography, buttons, and colors, which were standardized across projects. This toolkit helped ensure consistency while reducing the redundancy of design decisions across teams. The pattern libraries were integrated into Figma, enabling designers to access reusable components and avoid starting from scratch for each new feature.

UI Toolkit and Pattern Libraries

The next step was creating the UI toolkit and pattern libraries. These components included core elements like typography, buttons, and colors, which were standardized across projects. This toolkit helped ensure consistency while reducing the redundancy of design decisions across teams. The pattern libraries were integrated into Figma, enabling designers to access reusable components and avoid starting from scratch for each new feature.

UI Toolkit and Pattern Libraries

The next step was creating the UI toolkit and pattern libraries. These components included core elements like typography, buttons, and colors, which were standardized across projects. This toolkit helped ensure consistency while reducing the redundancy of design decisions across teams. The pattern libraries were integrated into Figma, enabling designers to access reusable components and avoid starting from scratch for each new feature.

Documentation and System Scalability

I set up clear documentation for every component within the design system. This involved using Figma and Confluence as centralized resources to track design decisions, usage guidelines, and best practices. The system was structured to be easily scalable, allowing future designers to onboard seamlessly and contribute effectively.

Documentation and System Scalability

I set up clear documentation for every component within the design system. This involved using Figma and Confluence as centralized resources to track design decisions, usage guidelines, and best practices. The system was structured to be easily scalable, allowing future designers to onboard seamlessly and contribute effectively.

Documentation and System Scalability

I set up clear documentation for every component within the design system. This involved using Figma and Confluence as centralized resources to track design decisions, usage guidelines, and best practices. The system was structured to be easily scalable, allowing future designers to onboard seamlessly and contribute effectively.

Output

1. Improved Workflow and Efficiency

The new workflow greatly improved the efficiency of both the design and development teams. The ticketing process ensured that every component was reviewed and documented thoroughly, while reducing miscommunication. Designers were able to access a centralized repository of assets, ensuring that the system remained consistent across updates​.

2. Cross-Team Alignment

The collaboration between design and development teams was enhanced, as the structured workflow allowed both teams to have clear expectations and feedback channels. By involving all stakeholders early on, we ensured the design system was viable both from a technical and design perspective.

3. Scalable Foundation for Growth

This pilot phase laid the groundwork for the design system to scale. The documented components, workflows, and collaborative structures provided a strong foundation for future iterations, enabling the system to evolve with the product. As a result, the design system became more than just a tool for consistency—it was a framework for sustainable design practices across teams.

Output

1. Improved Workflow and Efficiency

The new workflow greatly improved the efficiency of both the design and development teams. The ticketing process ensured that every component was reviewed and documented thoroughly, while reducing miscommunication. Designers were able to access a centralized repository of assets, ensuring that the system remained consistent across updates​.

2. Cross-Team Alignment

The collaboration between design and development teams was enhanced, as the structured workflow allowed both teams to have clear expectations and feedback channels. By involving all stakeholders early on, we ensured the design system was viable both from a technical and design perspective.

3. Scalable Foundation for Growth

This pilot phase laid the groundwork for the design system to scale. The documented components, workflows, and collaborative structures provided a strong foundation for future iterations, enabling the system to evolve with the product. As a result, the design system became more than just a tool for consistency—it was a framework for sustainable design practices across teams.

Output

1. Improved Workflow and Efficiency

The new workflow greatly improved the efficiency of both the design and development teams. The ticketing process ensured that every component was reviewed and documented thoroughly, while reducing miscommunication. Designers were able to access a centralized repository of assets, ensuring that the system remained consistent across updates​.

2. Cross-Team Alignment

The collaboration between design and development teams was enhanced, as the structured workflow allowed both teams to have clear expectations and feedback channels. By involving all stakeholders early on, we ensured the design system was viable both from a technical and design perspective.

3. Scalable Foundation for Growth

This pilot phase laid the groundwork for the design system to scale. The documented components, workflows, and collaborative structures provided a strong foundation for future iterations, enabling the system to evolve with the product. As a result, the design system became more than just a tool for consistency—it was a framework for sustainable design practices across teams.

Outcome

In just six months, I successfully laid the foundation for a scalable design system for Greator. By focusing on workflow, collaboration, and documentation, I ensured that the system not only solved immediate design challenges but also set the stage for future growth. The pilot design system proved the value of clear processes and cross-functional collaboration, creating a stronger, more cohesive product for the team and users alike.

Outcome

In just six months, I successfully laid the foundation for a scalable design system for Greator. By focusing on workflow, collaboration, and documentation, I ensured that the system not only solved immediate design challenges but also set the stage for future growth. The pilot design system proved the value of clear processes and cross-functional collaboration, creating a stronger, more cohesive product for the team and users alike.

Outcome

In just six months, I successfully laid the foundation for a scalable design system for Greator. By focusing on workflow, collaboration, and documentation, I ensured that the system not only solved immediate design challenges but also set the stage for future growth. The pilot design system proved the value of clear processes and cross-functional collaboration, creating a stronger, more cohesive product for the team and users alike.

Related Projects
Related Projects
Related Projects

E.

Currently available for product design roles
and system-driven projects on complex digital products.
If this way of thinking resonates, lets discuss a product.

© Edoardo Sportelli - 2026. Living in Italy, in Fiastra, nestled in the Sibillini Mountains. Like Tuscany, but better. Policy Privacy and Data Protection. No reuse or redistribution without permission.

E.

Currently available for product design roles
and system-driven projects on complex digital products.
If this way of thinking resonates, lets discuss a product.

© Edoardo Sportelli - 2026. Living in Italy, in Fiastra, nestled in the Sibillini Mountains. Like Tuscany, but better. Policy Privacy and Data Protection. No reuse or redistribution without permission.

Currently available for product design roles
and system-driven projects on complex digital products.
If this way of thinking resonates, let’s discuss a product.

© Edoardo Sportelli - 2024
Living in Italy, in Fiastra, nestled in the Sibillini Mountains. Like Tuscany, but better.

Policy Privacy and Data Protection.

No reuse or redistribution without permission.

E.