I’m a frontend engineer based in Brisbane, Australia. I make diagrams to understand complex ideas, explain how things work and discover what I haven’t quite understood yet.

Diagrams have been part of my professional life for years. When I was teaching myself frontend development, drawing a concept helped me follow the flow of data and instructions. It also exposed gaps in my understanding: a relationship I couldn’t explain, a missing step or a connection that didn’t make sense. That habit persisted. A diagram is often where I work through an idea before I try to explain it to someone else.

From drawing diagrams to building Diagrams.Design

For a long time, my diagrams were static, printable and designed to fit an A4 page. But I kept wanting to put them in motion.

A moving line could show where data was travelling. Revealing steps in sequence could make a complicated process easier to follow. And a diagram made for a printed page wasn’t always comfortable to read on a phone or watch as a video.

I wanted to design diagrams and animate them in the same place, with enough control to explain an idea clearly without making every animation a separate production. That was the starting point for Diagrams.Design: a tool shaped by something I wanted to use myself.

What I write about

Here, I write about diagramming, visual explanation and using motion to communicate ideas. My perspective comes from frontend development, but the questions always go beyond software. What should the viewer notice first? Which relationships matter? Where would movement make a process clearer?

I’m particularly interested in animation that earns its place: movement that shows direction, reveals a sequence or draws attention to a meaningful change. A static diagram lets people explore at their own pace. Motion gives me another way to guide them through it.

Krutie Patel

Frontend engineer, visual explainer and creator of Diagrams.Design.

Articles by Krutie