# Koa Health

Initiatives to make life easier for design team folks 🦄.

## The Context

⟦lead⟧ When I joined Koa Health the design team was **growing at fast pace**. We had 10+ designers in the organisation and having a designer's house prepared to scale fast and efficiently started to become a thing.

It's about establishing standards for process-heavy elements like project structure, file structure, component naming conventions, auto layout and naming of layers. It's not about adding complexity, but to **remove layers of uncertainty**.

I **started a series of small initiatives** that impacted lots of tasks in the designer's everyday work-life.

## Design Advocacy/Ops Initiatives

### File Covers

![Koa File Covers](/img/projects/koa/koa-filecovers-tags.png)

Also proposed ways to improve the organization of design files internally by defining a set of **"File Covers"** including workflow, environment identifier, title, status, initial date, JIRA ticket number, and owner.

The **goal** was to bring structured logic at workspace level and reduce time spent searching across teams.

### Boilerplate Starter Template

![Koa Starter Template](/img/projects/koa/koa-fileorg.png)

**"Starter Template"** — a set of pages to kickstart your projects. The **goal** was repeatable, scalable, shareable, easy to digest file structure used systematically across the team.

### Micro Workshops

![Autolayout workshop](/img/projects/koa/koa-file-microcourse.png)

When Figma released autolayout, I organized a **series of mini-workshops** for team members interested in digging more into autolayout and migrating design files.

### Contribution Commits

![Koa File Commit](/img/projects/koa/koa-filecommit.png)

By **commenting updates on shared libraries**, contributors can inform the team about the specifics of updates — keeping an updated contribution log and moving towards team transparency.

> **As long as we started to see small efficiencies compound, we knew we were moving in the right direction.**

As we continue to evolve, my hope is to reach a stage where tools and process fade into the background — and **I look back and wonder how we did it before**.