The Person Behind
the Framework
Before the system, before the science, before the language — there was a pattern that needed to be seen.
The work found me before I had a name for it.
I spent years building a career in human resources and organizational development — designing systems that helped companies understand performance, engagement, and talent. I was good at reading patterns in organizations. What I couldn't see were the patterns running me.
The same loops kept showing up. In my career decisions. In my relationships. In the way I responded to pressure, to uncertainty, to success. I could map an org chart but I couldn't map the operating system that was making my choices before I was conscious of them.
That disconnect is what led me to this work. Not a single moment of clarity, but a slow recognition that the patterns I was seeing in others were mirrors of the ones I was carrying.
Why I Built This
IAM Code-x™ came from the intersection of organizational systems thinking and personal emotional pattern work. It's a framework for understanding how emotional signals become behavioral patterns, how patterns stabilize into identity, and how that identity shapes everything — from the career you build to the relationships you choose to the version of yourself you present to the world.
I didn't create this framework to teach people what to feel. I created it because I needed a map. And once I had the map, I realized other people were looking for the same thing.
Training & Credentials
The framework didn't come from theory alone. It's grounded in certified methodology, lived practice, and ongoing study.
Built On
This framework doesn't exist in a vacuum. It's informed by the work of researchers, clinicians, and thinkers who have mapped the territory between neuroscience, behavior, and human potential. These are some of the voices that shaped the lens.
- neuroscience
- energy · body
- mathematics
- body code
- breath
- relationships
- psychology
- energy · identity
- science · spirit
- emotion mapping
I don't do this work because I've figured everything out. I do it because I've learned how to read the code. And I believe that once you see the pattern, you can't unsee it. That's where the real work begins.
Explore the FrameworkGet in Touch
A question about the framework, a thought about an episode, or an interest in working together — we’d like to hear it.
Thank you. Your message has been sent.