AI Strategy · Enterprise Architecture
Steven
Ruble.
Four decades of saying yes to the interesting problem.
Four decades of saying yes to the interesting problem.
A frontier enterprise architecture methodology that turns consulting work into something the client can use long after the engagement ends.
"A deck transfers understanding. An executable artifact transfers capability. Those are two different jobs."
For business owners who know something needs to change but aren't sure where AI actually fits.
"If your inventory clerk has five spreadsheets open to reconcile what the system says shipped — you're not ready for AI. That's where I start."
I start with the pain — what you think the problem is, what the team actually experiences, and where the real friction lives. That means talking to the people closest to the work, not just the people in the conference room.
I'll surface things that haven't been said out loud yet. That's not confrontational — it's how you get to the real problem instead of the surface problem.
We brainstorm, explore, and iterate until there's a path that makes sense for your business — not a generic framework, not someone else's best practice.
I leave you with a clear direction and the confidence to execute it. No ongoing dependency. No retainer you don't need. Just a path that's yours.
Steven Ruble didn't plan any of it. He said yes to interesting problems, stayed curious longer than most people thought was useful, and ended up helping to build a surprising number of things that we use every day.
Outside of work he chases live music — jazz, jam bands, anything that takes a melody somewhere unexpected. Artists who find new ways to express something familiar. He's re-learning guitar and piano — and learning how to write his own lyrics and music.
It took him a while to realize he'd been doing the same thing with technology his entire career. Finding new ways to use existing technology in inventive new ways. The melody was always there. He just kept asking what else it could sound like.
I've spent my career at the edge of what technology could do — not behind it, not ahead of it, but right at the moment when something new became possible. And helping clients take advantage of that moment.
I never really planned a career. I was just always pulled toward whatever was newest, most unproven, most likely to matter. From hand-writing COBOL code submitted to key-punch operators, to accidentally helping blueprint what became the modern smartphone, to building the first system that let someone buy and activate a mobile phone online, to designing the operational architecture for the LA2028 Olympic Games.
Today I'm helping companies figure out how AI actually fits into the way their business runs — not as a feature someone bolted on, but woven into the work itself until people stop noticing it's there.
What I actually do — whether I'm inside a Fortune 500 or sitting across from a business owner trying to make sense of all the AI noise — is figure out what to build and why, before anyone touches a keyboard. I ask the questions nobody's asked yet. I talk to the people doing the real work. And I help you find a path forward that feels like yours, because it is.
Explore the full career archive →He accidentally helped assemble the conceptual blueprint for what became the modern smartphone.
No agenda. No pitch. Just a conversation about what you're trying to figure out.