Evisions

Scaling UX Consistency and Hand-off: How we restructured the design process to reskin 130+ pages under tight deadlines and legacy CMS constraints.

Role

UX/UI Designer & Design Ops

Role

UX/UI Designer & Design Ops

Role

UX/UI Designer & Design Ops

Role

UX/UI Designer & Design Ops

Project type

Commercial Project (Website Redesign)

Project type

Commercial Project (Website Redesign)

Project type

Commercial Project (Website Redesign)

Project type

Commercial Project (Website Redesign)

Project scope

Timeline

3 Months (Autumn 2025)

Timeline

1 month (November 2024)

Timeline

3 Months (Autumn 2025)

Timeline

1 month (November 2024)

Team

Internal UX Team, Frontend & Backend Devs, Copywriters, Dept. Managers

Team

Internal UX Team, Frontend & Backend Devs, Copywriters, Dept. Managers

Team

Internal UX Team, Frontend & Backend Devs, Copywriters, Dept. Managers

Team

Internal UX Team, Frontend & Backend Devs, Copywriters, Dept. Managers

Tools

Figma, Google Docs, Strapi CMS

Tools

Figma, Google Docs, Strapi CMS

Tools

Figma, Google Docs, Strapi CMS

Tools

Figma, Google Docs, Strapi CMS

AI

ChatGPT, Gemini, NotebookLM, Recraft, Relume

AI

ChatGPT, Gemini, NotebookLM, Recraft, Relume

AI

ChatGPT, Gemini, NotebookLM, Recraft, Relume

AI

ChatGPT, Gemini, NotebookLM, Recraft, Relume

UX/UI Design

UX/UI Design

Design Ops

Design Ops

Commercial Project

Commercial Project

Responsive Web

Responsive Web

#hero —

#nav-trigger-1 —

The context

How an outdated website prompted a complete In-house system rebuild

Evisions was relying on an older website that no longer reflected its scale, identity, or way of working. The visuals were outdated , the structure didn't support current services , and the user experience failed to showcase the company's expertise , especially as a newly formed internal UX team was gaining visibility.

The team decided to rebuild the website in-house, aiming to create a stable, scalable platform with solid UX, full content control, and a structure that genuinely reflected how evisions communicates with clients.

#context —

My Dual Role:
UX & Design Ops

Stepping in to provide structure and clarity
where the team needed it most

I joined the project after initial visual mockups were created. My role was dynamic, focused on bringing structure and clarity wherever they were most needed. I saw my contribution less about polished screens and more about supporting the team through the practical, often invisible, parts of website building.

My responsibilities included: mobile UI logics (recrafting existing desktop views to mobile), hand-off preparation, CMS work, and content coordination.

#research —

Key Contributions
and Process Impact

Transforming chaos into a predictable workflow
through structured documentation

Key Contributions
and Process Impact

Transforming chaos into a predictable workflow through structured documentation

Architecting the development hand-off

Unstructured mockups lead to wasted development time and increased errors. I countered this by proactively building a complete, transparent hand-off.

  • Action: I reorganized Figma files, extracted elements into reusable components, and established a lightweight UI kit complete with variables for typography and spacing.

  • Impact: This system became the single element maintaining logic and consistency across 100+ pages. The rigorous structure reduced clarifying messages and accelerated the development team's velocity. A clean, structured file is essential; it saves the entire team critical hours.

Architecting the development
hand-off

Unstructured mockups lead to wasted development time and increased errors. I countered this by proactively building a complete, transparent hand-off.

  • Action: I reorganized Figma files, extracted elements into reusable components, and established a lightweight UI kit complete with variables for typography and spacing.

  • Impact: This system became the single element maintaining logic and consistency across 100+ pages. The rigorous structure reduced clarifying messages and accelerated the development team's velocity. A clean, structured file is essential; it saves the entire team critical hours.

Defining content structure (Product coordination)

Due to critical time constraints, scalable documentation was initially lacking.

  • Action: I countered the inefficiency by structuring all content documentation in Google Docs, detailing context, stylistic recommendations, and templates for every section.

  • Impact: This system proved vital, successfully preventing multiple content rewrites and reducing content-related meetings to just one.

Defining content structure
(Product coordination)

Due to critical time constraints, scalable documentation was initially lacking.

  • Action: I countered the inefficiency by structuring all content documentation in Google Docs, detailing context, stylistic recommendations, and templates for every section.

  • Impact: This system proved vital, successfully preventing multiple content rewrites and reducing content-related meetings to just one.

Addressing UX debt (Mobile logic)

The initial desktop-first approach created friction, necessitating the removal or simplification of elements to ensure mobile performance. I contributed by recrafting existing desktop views to define the necessary mobile UI logics.

#contributions —

Outcome
and Retrospective

Validating the theory: structure and process
are as important as pixel-perfect screens

Outcome
and Retrospective

Validating the theory: structure and process are as important as pixel-perfect screens

The team successfully delivered a fully rebuilt website across 130+ pages within three months.¨

Qualitative Impact: Feedback confirmed the process felt "noticeably smoother" compared to previous iterations—experiencing fewer bottlenecks and last-minute surprises. The structure I introduced successfully reduced operational friction for the entire team.

#system —

Reflection &
Key Takeaways

Design is organization

This project demonstrated that structure and process create as much impact as perfect screens. Design is ultimately about organizing how people, information, and tools interact for systemic success.

Mobile-first mandate

I would insist on a mobile-first approach upfront; scaling up is easier and yields a more resilient design

Internal UX matters

A well-built hand-off is a form of internal UX that shapes the team’s experience and, critically, the final product quality.

Prioritize documentation tools
Prioritize documentation tools

The necessity to insist on a proper scalable documentation system (at least Notion for small projects) and clarify ownership must happen at the project's inception.

#context —

#reflections —

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —

What will we build?

© Ekaterina Pykhova, 2025

#footer —

#contact —