I design the structure first.
The screens come after.
I lead design at 834 Labs, where I built the design system behind five products and the multi-role platform that admins, agents, and sub-agents all work in. I like problems where who sees what, which fields depend on which, and how a legacy process becomes one screen matter more than the color of the button. I build a lot of what I design, so the handoff is real.
Open to Senior Product Designer roles at B2B software companies. Dallas-based, open to remote.
I don’t open Figma until the problem makes sense.
I start with the permission model, the data architecture, the user’s mental model of what they’re actually trying to do. For MyAdmin360, the architecture came before any visual decision, because for multi-role platforms navigation IS the product. The visual work lands only because the structural work is solid.
I’m best on problems where the complexity is structural. Multi-role platforms where the same data needs to look completely different depending on who’s logged in, or legacy systems where users have built years of workarounds you have to respect while still improving things. Simplification means rebuilding the system, not just the screens.
I use AI heavily for research synthesis, rapid prototyping, and proof-of-concept builds. I built the MyAdmin360 interactive prototype solo using Claude, deployed it live at app.myadmin360.com, and presented it to stakeholders. It’s become my default way of validating ideas fast before committing to full design.
Navigation, permissions, and data hierarchy come before the first frame. Get the structure wrong and every screen that follows it will also be wrong.
User interviews, workflow shadowing, heuristic audits. Every major decision needs a reason that isn't "I think." That's how I push back on bad ideas without making it personal.
One polished screen is a deliverable. The real output is a design system that lets engineers build new features without coming back to design every time.
Enterprise products carry a lot of data. The job isn't to remove it. It's to build visual patterns so consistent that users navigate the complexity without having to think about it.
Before product, I spent years in print. That is where the precision comes from.
I spent six years as a designer at Living Magazine, laying out feature spreads, managing print production, and building visual systems under real deadline pressure. Print doesn’t iterate. You get it right before it goes to press, or it’s wrong in 30,000 copies. That builds a different kind of eye.
When I moved into product design, the typography rigor, the layout instincts, and the care about spacing and hierarchy all transferred. What changed is what comes before them: user research, permission models, data architecture. The print years are why my dashboards look finished. The product years are why they work.
I have a BFA in Graphic Design from the Art Institute of Dallas and a UI/UX certification from Springboard, but most of what I know came from doing it. Currently I’m Lead Designer at 834 Labs (full-time) and co-founder at InnoGEV on the side. The two roles together have taught me more about product design in two years than anything else.
The role where design is the hard part, not the afterthought.
I’m looking for a Senior Product Designer seat on a B2B product with real structural depth: multi-role platforms, data-heavy workflows, legacy systems that need rebuilding rather than reskinning. Design systems work is a plus. I’m in Dallas and open to remote. The domain matters less to me than whether the team takes design seriously early.
I’m most useful before the scope is locked. If design only enters after engineering has scoped the work, you’re paying for a skin, not a solution. The conversations I care about are the early ones, where tradeoffs are still being weighed and the right design question can change what gets built entirely.
I push back when I need to, but always with something to back it up. On AgilityFMO, stakeholders kept wanting to add content to the homepage. I used agent research to show exactly which actions were getting buried and how many clicks it added to the contracting flow. That kind of conversation is easier when the data is doing the talking.
Have a complex problem
that needs untangling?
Open to Senior Product Designer roles at B2B software companies, remote or Dallas. I do my best work on multi-role platforms, legacy modernization, and 0→1 builds where the structure has to be right before the screens can be.