How I Get Through Creative Burnout

Burnout is real. You can’t avoid it forever, but you don’t have to let it tank your progress. Here’s how I keep going when the spark’s gone.

A wooden cube teeters on the edge of a rectangular block against a plain background.

How Burnout Shows Up

Burnout sneaks up on you. One day you’re excited. The next you’re staring at a blank page, dreading the work. Sometimes it’s exhaustion, sometimes it’s boredom, sometimes you just can’t make yourself care. It happens to everyone, no matter how much you love what you do.

What I Stop (and What I Keep)

When I feel burnout coming on, I cut everything nonessential. No new projects. No extra commitments. I focus on the basics—one piece of content, one small win at a time. I let myself take breaks, even if it feels like I’m falling behind. What I don’t stop: showing up in small ways. Even a half-finished draft is progress.

Getting Back to Work Without Starting Over

Burnout isn’t permanent. When the energy comes back, I start slow. I don’t try to catch up all at once. I make a short list—what needs to go live this week, what can wait, what can be skipped. I try to remember why I started in the first place. Progress is progress, even when it’s slow. You don’t have to be on fire to get things done. You just have to keep moving.

Frequently Asked Questions

You need Figma Console MCP installed in Claude Desktop. Once set up, Claude uses the figma_post_comment tool to pin comments to specific layer node IDs. You ask Claude to run a review and post violations — it handles both steps automatically.

Use Figma Console MCP's figma_get_file_data tool via Claude Desktop. It reads all text layers from your open Figma file — including layer names, text content, and node IDs — through the Desktop Bridge plugin. No exports, no copy-paste.

Yes. In your review prompt, ask Claude to review multiple frames by name. Claude reads all of them, checks against your guidelines, and posts comments across all screens. Expect 3–5 minutes for multiple screens.

About 15–20 minutes total — most of that is downloading Node.js if you do not have it. The configuration steps themselves take under 5 minutes. After setup, every content review takes 3–5 minutes.

Be the first to know about every new letter.

No spam, unsubscribe anytime.