Explaining Technical Things in Plain Language Is a Creative Skill
For a long time, I didn’t think explaining technical things had anything to do with creativity.
Creativity lived in photos and videos. In visuals, instincts, and taste. Technical explanations felt like something else entirely. Dry. Mechanical. Necessary, maybe, but not expressive.
That way of thinking stuck with me for years, and I didn’t really question it until I noticed how often people would thank me not for what I made, but for how I explained something. A process. A workflow. A decision. A piece of code. A system.
That’s when it started to click.
Explaining technical things in plain language is a creative skill.
Knowing something isn’t the same as understanding it. And understanding it isn’t the same as being able to explain it. It’s easy to sound smart by using jargon. Acronyms. Complicated language that feels impressive but leaves the other person nodding without actually following along.
Clarity takes more effort.
Whenever I try to explain something technical to someone non-technical, it forces me to confront my own thinking. If I can’t explain it simply, there’s a good chance I don’t understand it as well as I thought I did. That realization is uncomfortable, but it’s useful. It exposes where my thinking is solid and where it’s still fuzzy.
That process feels a lot like creative work.
You slow down. You choose words carefully. You decide what matters and what doesn’t. You remove noise without removing meaning. That’s not mechanical. That’s intentional.
There’s a common misconception that explaining something simply means dumbing it down. I don’t see it that way anymore. Simplicity isn’t about removing depth. It’s about removing friction. It’s about making something usable instead of impressive.
That mindset carries directly into how I approach creative work.
Good photography communicates something, even if it’s subtle. Good writing does the same. You don’t need mystery for the sake of mystery. You need clarity that invites someone in and lets them engage on their own terms.
The same applies to technical explanations.
Over time, I realized this is where my technical side and my creative side actually meet. They aren’t competing. They’re collaborating.
My technical brain wants structure, logic, and systems. My creative brain wants flow, expression, and meaning. Explaining technical ideas in plain language requires both. You need precision, but you also need empathy. You have to know the material well enough to shape it for someone else.
That’s creativity.
This skill shows up constantly in my work, even when it’s invisible. When I explain what to expect from a shoot. When I walk someone through a process without overwhelming them. When I translate abstract ideas into something actionable. When I make someone feel comfortable instead of intimidated.
Clarity builds trust.
Most people don’t need to understand every technical detail. They just need to feel confident that you do, and that you can guide them through it without making them feel small or lost.
I’ve also learned that simplicity is usually a sign of experience. Early on, it’s tempting to explain everything. Every choice. Every setting. Every reason. Over time, you realize most people don’t need all of that. They need the right amount of information at the right moment.
Knowing what to leave out matters as much as knowing what to include.
That restraint doesn’t come from shortcuts. It comes from repetition. From years of doing the work and seeing what actually helps people move forward.
Creativity isn’t just about making things look good. It’s about helping people understand. Helping ideas move. Helping complexity feel manageable.
Whether I’m taking photos, building systems, writing, or explaining a single line of code, the goal is the same.
Reduce friction. Increase clarity. Create space.
That’s not just technical skill.
That’s creative work.