How to Get Your Company to Let Designers Start Writing Code

I have been talking to designers about how empowering it is to deliver designs as final code, and one theme I keep hearing is, “I love this idea, but I don’t think my company would ever let me try it.”

Here is a proven playbook to get your company to allow designers to start writing code:

1. Start with low-risk UI-only bug fixes

Think spacing issues, color swaps, and updating font styles. These are simple non-functional fixes that improve the experience but are work most engineers do not want to spend their time on. Make engineering feel like you are taking work off their plate without introducing risk.

2. Commit to no “vibe coding”

Make it clear that you are not going to let AI run free in the codebase. Every change you submit should be deliberate, manually updated, and something you fully understand. Use AI to suggest code updates and navigate the codebase, but do every update yourself. When engineers hear that designers want to write code, their first thought will likely be of vibe coding and all the trouble it could cause. Show them this is not the case.

3. Follow engineering’s process and standards

Follow the same processes engineers do from start to finish. Explain that you are going to make branches and go through code review. Run the same tests and follow the same QA process. Create tickets and learn naming conventions for branches and pull requests so your contributions fit smoothly into their workflow. If you are going to go through code review and use all the same processes, they will not be worried about code quality.

4. Ask for the same permissions they give to engineering interns

In addition to engineering buy-in, you will also need access from IT or Security for Git repositories and coding tools. If they hesitate after you go over items 1 through 3, explain that you only want the same permissions they give to engineering interns. If they trust 20-year-old interns with that access, they can trust designers with years of experience.

5. Build trust slowly

Start with very small fixes. If something looks more complex than you expected, leave it for now. The goal is to prove that designers can contribute safely without creating headaches. Once engineers see your code is useful and reliable, they will invite you to do more.

The payoff

Handoffs disappear, design QA goes away, the gap between design and code closes, designers get to polish the experience in the final medium, and engineers can focus on more complex work.

It is better for the team, the business, the users, and a big step forward for design.

I have been training my team and others to do this with AI, and the results have been huge. Learn more at CraftAmplify.