---
title: "Sketch | Skills We Assign For | Azendo"
description: "Sketch on existing design estates — libraries, migration questions, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/sketch/"
---

[Skills](https://azendo.co/skills/) Design and research 

# Sketch.

Sketch is a macOS interface design application with symbols, shared libraries and a plugin ecosystem. It was the dominant tool before collaborative browser-based design and remains in use on established products.

## Where Sketch fits on a long engagement.

Sketch files are a real asset on products with design history. Years of components, patterns and decisions live in them, and migrating to another tool is genuinely lossy — component structure, overrides and library relationships do not transfer cleanly.

The practical constraints are collaboration and platform. Real-time multi-person editing is not its model, and being macOS-only excludes anyone else from opening a file. For distributed teams those are the reasons migrations happen, more than any feature comparison.

## What an assigned team does with Sketch.

Migration decisions should follow team need rather than tool fashion. A small co-located design team with a mature Sketch library has little to gain; a distributed team where stakeholders cannot open files has a concrete problem.

Making that assessment honestly rather than recommending the current default is how we approach existing estates, and it is part of the scoping covered in [how the monthly fee is built](https://azendo.co/pricing/).

## What we use Sketch for.

* Existing libraries maintained Working within the established system rather than migrating without a reason.
* Migration assessed on real cost What transfers and what is rebuilt, established before committing.
* Collaboration constraints named Platform and editing limits weighed against the value of the existing files.

## How Sketch capacity is assigned.

Design capacity is assigned under [outsourced design team](https://azendo.co/services/ux-ui-design/), working in the tool the estate already uses unless there is a concrete reason to move.

## Service lines it sits in

* [UX/UI design](https://azendo.co/services/ux-ui-design/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in design and research

* [Storybook — skill we assign for](https://azendo.co/skills/storybook/)
* [Maze — skill we assign for](https://azendo.co/skills/maze/)
* [Hotjar — skill we assign for](https://azendo.co/skills/hotjar/)
* [usability testing — skill we assign for](https://azendo.co/skills/usability-testing/)
* [design systems — skill we assign for](https://azendo.co/skills/design-systems/)
* [design tokens — skill we assign for](https://azendo.co/skills/design-tokens/)
* [component libraries — skill we assign for](https://azendo.co/skills/component-libraries/)
* [Figma Dev Mode — skill we assign for](https://azendo.co/skills/figma-dev-mode/)

## Tell us what your roadmap needs Sketch for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)