01
Fragmented visual workflow
Inspirations, product images and collection ideas were stored across different tools, making it difficult to see the full creative context in one place.
I designed a visual workspace that allowed fashion and retail teams to organize projects, inspirations, product images and AI-generated concepts directly within a SaaS PLM platform.
SilkPLM is a B2B SaaS platform supporting fashion, home decor and retail teams in managing products, collections and related development data.
The Collection Workboard was designed as a visual workspace where designers and other product teams could organize inspirations, projects, product images and AI-generated concepts without leaving the PLM environment.
The project extended an existing product, so the solution had to work with SilkPLM’s architecture, design system and available development resources. Selected parts of the concept were later implemented in the platform.
SilkPLM provided structured product and collection data, but teams lacked a flexible visual space for organizing inspirations, projects and product concepts within the platform.
Inspirations, product images and collection ideas were stored across different tools, making it difficult to see the full creative context in one place.
Designers had to move between the PLM system and external visual tools such as Miro or Canva, which interrupted the workflow and separated creative decisions from product data.
Projects, inspirations and generated assets needed to remain connected with the products and collections already managed inside SilkPLM.
The new feature had to fit the existing system architecture, interface patterns and design system while remaining realistic for a startup development team.
I worked as a UI/UX Designer responsible for translating the initial product idea into a structured workflow and interface that could become part of the existing SilkPLM platform.
I mapped how users could create a workboard, add content, access existing materials and manage selected items on the visual canvas.
I designed the main workboard views, contextual image actions, supporting panels and connections with other areas of SilkPLM.
I reviewed the feature with the Project Manager and a fashion specialist, then discussed technical feasibility with developers.
I contributed to designing and testing AI-related flows in SilkPLM, including the AI Pattern Generator. The technical AI integration was outside my role.
The discovery process combined competitor analysis, internal domain knowledge and iterative reviews with product and development stakeholders.
I reviewed visual workspace patterns used in products such as Miro and Canva, focusing on canvas interaction, adding content, contextual actions and organizing visual materials.
A fashion specialist provided practical knowledge about how collection teams work with products, references and inspirations. This helped define the content users needed on the workboard.
The Project Manager reviewed the feature concept and supported the definition of requirements, priorities and connections with other parts of the SilkPLM platform.
I discussed selected interactions with developers and refined the designs according to the existing architecture, available components and implementation constraints.
Projects, products and inspirations should remain available inside the visual workspace.
Familiar drag-and-drop patterns could reduce the learning curve.
AI-generated materials should support an existing collection workflow instead of becoming a separate destination.
Reusing the existing design system would make the feature more realistic to implement.
The concepts were reviewed internally by the Project Manager and fashion specialist. This provided product and domain-expert feedback, but it was not a formal usability study with end users.
After mapping the main user paths, I prepared an early workboard concept to communicate the feature direction and discuss how a visual workspace could fit into the existing SilkPLM platform.
At this stage, the focus was on information structure, access to collection materials and the relationship between the canvas and supporting tools—not on final visual details.
Feedback from the Project Manager and fashion specialist helped me refine the feature scope before moving to detailed interface design and technical discussions with developers.
The final concept brought collection materials, project data, inspirations and AI-assisted content into one visual workspace.
Instead of moving between the PLM system and external tools, users could access existing materials, place them on the canvas and manage selected items without losing the product context.
The main workboard provided an open canvas where users could visually organize collection materials by dragging, positioning and grouping images according to their needs.
Contextual controls appeared after selecting an item, keeping the default workspace focused while providing access to additional actions when needed.
The default view combined the visual canvas with existing SilkPLM navigation, collection tabs and collaboration features.
Users could browse projects and inspiration galleries already available in SilkPLM without leaving the workboard.
After selecting an item, they could drag its images directly onto the canvas and position them alongside other collection materials. This connected visual exploration with structured project data.
Existing projects and inspirations could be reused directly instead of being exported and uploaded again.
The concept also provided access to AI generation tools available within the SilkPLM product ecosystem.
Users could define generation settings, review generated results and add selected images to the workboard or save them as inspirations for later use.
My contribution focused on designing and testing AI-related user flows. The technical integration of AI services was outside my role.
When an image was selected, the interface displayed actions relevant to that item.
Depending on the content, users could reposition the image, access its options, add comments, save it as inspiration, download it or remove it from the workboard.
Contextual actions reduced interface clutter by displaying additional controls only when an object was selected.
The interface decisions focused on connecting visual exploration with existing product data, reducing unnecessary tool switching and keeping a complex workspace understandable.
The workboard was designed as part of the PLM ecosystem rather than as an isolated canvas. Users could access projects, inspirations and collection data from the same workspace.
Materials already stored in SilkPLM could be added directly to the board, reducing the need to export, download and upload the same assets between different applications.
Drag-and-drop interaction allowed users to add and organize visual materials in a way that was familiar from other canvas-based tools.
Image actions appeared after selecting an item. This kept the canvas focused while making editing, comments and asset options available when they were relevant.
Existing navigation, components and visual patterns were reused to reduce the learning curve and make the feature more realistic for the development team to implement.
AI-generated content was treated as another source of inspiration within the collection process instead of becoming a separate, disconnected product area.
These decisions show how I balanced user needs, domain requirements, existing product architecture and startup development constraints while designing a complex B2B SaaS feature.
The project established a structured direction for a visual collection workspace integrated with the existing SilkPLM product. Selected parts of the concept were implemented, while the broader solution remained a direction for further product development.
The project translated an initial idea into a documented workflow, interface concept and set of interactions that could be discussed and prioritized by the product team.
The concept connected visual collection work with projects, inspirations and content already available inside the PLM system.
Reusing existing product components and discussing feasibility with developers helped keep the solution aligned with the platform’s architecture and available resources.
Selected elements of the concept were implemented in SilkPLM. The remaining flows and interface ideas created a foundation for further development of the feature.
The project was reviewed internally and partially implemented, but I do not have verified quantitative usage or business metrics. Therefore, I evaluate the outcome through the completeness of the workflow, stakeholder feedback and its connection with the existing product architecture.
Formal usability testing with target end users was not part of the project scope.
This project helped me better understand how to introduce a complex feature into an existing B2B SaaS product while balancing user needs, domain knowledge, technical feasibility and startup constraints.
Collaboration with a fashion specialist helped reveal workflow requirements that would have been difficult to identify through competitor analysis alone.
Designing a new SaaS feature requires understanding how it connects with existing navigation, product data, components and technical architecture.
Reusing established UI patterns reduced unnecessary design work, improved consistency and made selected parts of the concept more realistic to implement.
AI-generated content created more value when it became part of the collection workflow instead of functioning as a separate, disconnected feature.
The project strengthened my ability to turn an early product idea into a structured user flow and interface concept, collaborate with specialists and developers, and make design decisions within the realities of an evolving startup product.