I've Always Been Drawn to Making Things Work Better
My career has moved through video, design, user experience, leadership, systems, and knowledge architecture.
The work kept changing, but I kept gravitating toward the same kind of problem: figuring out what was getting in the way and finding a better way forward.
It Started with Storytelling
My first creative work was not designing websites or building systems. It was editing video.
Every cut shapes how a story unfolds. What you include, what you leave out, and what comes next all influence what someone notices and how they experience it.
Good editing is not simply about making something shorter. It is about deciding what matters, creating the right sequence, and helping the audience follow the story without losing what makes it meaningful.
I did not realize it at the time, but I was already learning to think about an experience from the perspective of the person moving through it.
The Work Kept Changing
Editing led to graphic design. Graphic design led to websites. Websites led to user experience, design systems, leadership, internal processes, and knowledge architecture.
Each discipline introduced new tools and different kinds of problems, but I kept returning to similar questions:
What is someone trying to accomplish? What is getting in the way? Why is it happening? What would actually help?
Sometimes the answer was a clearer interface. Sometimes it was better language, a different process, stronger documentation, or an entirely new system.
The form of the work kept changing. The way I approached it became more consistent.
The Pattern Became Clearer
For a long time, I thought I was simply interested in solving problems.
Eventually, I noticed that the problems I enjoyed most often involved something getting in the way of what people were trying to accomplish.
A customer could not tell which option was right. A team might be solving the same problem in different ways. Important knowledge existed but was difficult to find or apply. A process worked, but required more effort than it should.
The problems looked different, but I was approaching them in a similar way: understand the goal, find what was getting in the way, and figure out what needed to change.
That realization changed where I started. Instead of beginning with what to build, I started by asking what problem actually needed to be solved.
I Kept Following the Work
I did not set out to become a UX designer, lead teams, build design systems, or create knowledge architectures.
I kept saying yes to problems that needed solving.
Each one required me to learn something new and expanded the way I thought about design. Over time, I stopped thinking about design as something limited to a screen or a specific discipline.
It could shape an interface, but it could also shape language, information, a workflow, a process, or the way a team works together.
Looking back, the path feels surprisingly consistent, even though it did not feel that way at the time.
Why Atomic Pineapple?
The name brings together two ideas that have shaped the way I work.
Atomic
“Atomic” was inspired by Atomic Design and the idea that larger systems are built from smaller reusable parts.
That way of thinking changed how I approached design. Instead of solving the same decisions repeatedly, I began looking for patterns, rules, and components that could make good decisions easier to reuse.
The individual pieces may be small, but together they create something that can grow and adapt.
Pineapple
The pineapple represents hospitality.
Good hospitality means thinking ahead about someone else’s experience. It means anticipating likely needs, respecting people’s time and attention, and removing unnecessary effort wherever possible.
That idea applies far beyond customer service. It can shape an interface, an instruction, a process, or any experience someone has to move through.
Atomic Pineapple brings those ideas together: thoughtful systems built around people.
The Story Isn’t Finished
Today, I spend less time editing video and more time thinking about products, teams, systems, leadership, and organizational knowledge.
The problems are different, but I am still drawn to the same kind of work: understanding what someone is trying to accomplish, figuring out what is getting in the way, and finding a better way forward.
Atomic Pineapple is a place to share what I have learned, explore what I am still learning, and document the ideas that continue to shape the way I work.
Atomic Principles. Served with Aloha.