How OOUX transformed my UX consulting practice (and how it can transform yours)

How one methodology eliminated endless revisions, built instant client trust, and transformed messy requirements into clear designs.

Allie offering guidance as a team works through the structure of their system during an OOUX workshop.

I didn’t realize how much weight I was carrying as a consultant until the day a new client looked at me with that half-defeated expression and said, “We’ve been working with another firm for months… they just don’t get us.”

If you’ve ever consulted in the world of UX design, you probably know exactly what that moment feels like. You’re suddenly handed years of accumulated complexity and frustration, and expected to “figure it out” quickly, gracefully, and without disrupting existing workflows or politics. On the outside, you’re confident and calm. On the inside: Okay… where do I even start?

For years, this was my everyday reality working as a UX consultant. I’d be dropped into legacy rebuilds, brand-new product concepts, unfamiliar domains, and tangled stakeholder groups. I was expected to design the experience while juggling multiple projects, fitting into whatever process the team already had, and producing polished work without much time to deeply understand the system behind what I was designing. I tried so many methodologies, frameworks, and workshop styles. Yet no matter what I did, I always found myself in revision loops, clarifying misunderstandings that should have been surfaced sooner, and discovering that I had spent days (or weeks!) exploring a design direction that didn’t match what the business actually needed.

I was exhausted and frustrated with myself for not having a way to reliably get to clarity faster. I wanted a process flexible enough to use with any project, but structured enough to help me avoid those heartbreaking moments where I’d realize far too late that the thing I had designed was built on a shaky or incomplete understanding of the system.

In 2020, right in the middle of the pandemic, I took a workshop on Object-Oriented UX (OOUX) with Sophia Prater, and it clicked immediately. Her ORCA process (which stands for objects, relationships, calls-to-action, and attributes) gave me a simple way to break down complex systems and product requirements so our team could actually understand what we needed to design and develop. It wasn’t abstract or theoretical. It’s one of the only things that actually helped me quickly see what was happening underneath the surface of a product, and gave me a path for mapping that system directly with stakeholders. It was a game changer.

Fast forward after getting certified as an OOUX strategist, I found myself meeting with a new client. They were frustrated from an unproductive discovery with another consultancy and weren’t sure where to go next. Instead of walking through their sitemap or asking for a list of features they wanted, I simply began asking them about the things that mattered most in their world:

“What’s an example of a practice?”

“How does that relate to your focus areas?”

“How many services do you provide?”

As they talked, I opened a Miro board and began casually modeling the objects I was hearing on blue sticky notes, drawing arrows between them for how they related, and asking more clarifying questions about different instances of them. I didn’t frame any of it as a method. I was just tyring to understand them through their ORCA.

After a half-hour or so we formed the start of an Object Map (which if you’re not familiar is a visual representation of a system with objects across the top and attributes like core content, metadata, and nested objects listed below in a column.)

An example Object Map of an organizations system

It was at this point one of the clients looked at the screen, and said, “Oh my gosh… you actually understand us.”

I continued using the ORCA process and creating object maps with clients, and the same thing kept happening. Stakeholders relaxed, and opened up. They felt seen and understood because we were literally making sense of their world together. It took what used to be one of the most stressful parts of consulting, gaining trust quickly, and made it effortless. And from my side, I wasn’t guessing anymore or designing blind. I finally had a way to understand a system before I was expected to design a new experience.

A participant walking through an object map during an OOUX workshop, as Allie and other participants look on and discuss the structure together.

One of the best examples of this was a project involving decades-old livestock management software. It was a massive system that had grown and adapted over the years, long after the original developers had left. Everyone knew it was critical to the business, but no one could fully articulate how it actually worked under the hood.

I started discovery work by facilitating an ORCA Sprint, where we spent a week together mapping the system’s objects (CLIENT, BARN, INVOICE), the relationships between those objects (a BARN has many INVOICES), the actions you could take on those objects (an account manager posts an INVOICE), and the structural attributes that differentiated each object instance (an INVOICE has a Name, Date, Status).

A working snapshot from a Miro board used during an ORCA Sprint to document attributes from an existing system ahead of a redesign.

And through the activities the fog lifted and the monolith became understandable. We could all see what belonged in the MVP re-build, what was strategically important to build together in phases, and how the pieces over time would create a system that would replace their old one. In just a week of collaborating, we all had a clear understanding of how the system worked, what we needed to build, and a more accurate roadmap and scoped budget the team could actually deliver on. We used that knowledge and understanding throughout the multi-year re-build of the system, continually referencing and iterating on the object map we created together.

[embed]**See how Allie used OOUX to re-design a custom legacy invoicing and inventory software.** www.allieofisher.com

But the power of OOUX and the ORCA process isn’t limited to just understanding existing systems. I’ve used ORCA Sprints just as effectively on brand-new product concepts. When paired with strong product owners who have a clear vision, ORCA created a structured and collaborative way to explore an idea, bringing the “forest” and the “trees” into focus at the same time. It helped us uncover API needs early, surface hidden dependencies, plan for screen designs systematically, and test assumptions before investing in iteration after iteration of prototypes and concept designs. OOUX revealed the knotted areas before they became costly, and it helped our team move forward with confidence instead of uncertainty.

[embed]**See how Allie used OOUX to conceptualizing a new product concept**www.allieofisher.com

What I’ve grown to appreciate most about OOUX is that it’s not a black-box consulting trick. I’m not disappearing for weeks, re-emerging with designs, and hoping they resonate. It’s collaborative from the start, giving clients I’ve worked with a clear, structured way to make decisions. They’re not relying on trust alone — they understand why something needs to be designed a certain way because they can visually see the system logic and their business reflected back at them.

A team sitting around a table covered with blue sticky notes, discussing which objects are most relevant to the system they’re designing.

For consultants, this is everything! Our work depends on understanding new environments quickly, asking the right questions, and making smart recommendations with limited time. Traditional discovery can sometimes feel like you’re fumbling around for fragments and hoping they eventually form a complete picture. With ORCA, the picture emerges early and clients can feel that. They see progress in every conversation rather than waiting for a big reveal. And I stopped second-guessing myself because I was grounding every design decision in the structure of the system.

Over time, I realized that OOUX didn’t just make me more efficient; it made me a better consultant. My stress decreased and my confidence increased. Clients trusted the process because they could see the clarity it brought when talking through requirements and prioritizing what mattered most.

A group of people seated around a table, arranging colorful sticky notes to create an object map during a workshop.

And, you don’t need to adopt the entire ORCA process at once to feel its impact! Start small. Try to identify the primary objects in your system, talking about what makes each distinct, or which is the most important to the business (we call those revenue objects!). Try a mini ORCA Sprint with a team that’s struggling to articulate their needs for a new feature. Use the process to make sense of a domain you’re new to. I think you’ll be surprised at how quickly the work becomes easier (and more fun!) and how quickly teams start saying things like, “No one has ever helped us understand our system this way before.”

That’s why I advocate for this process so strongly. It’s not because it’s trendy or clever. It’s because it works. It helps designers and teams cut through complexity, avoid unnecessary rework, and build products that are grounded in real structural understanding. And in the world of UX consulting (where clarity and trust are everything!) that’s transformative.

If any part of this story resonates with you I’d genuinely love to talk! These conversations have become some of the most energizing parts of my work.

Feel free to reach out, share your experience, or ask questions. If you’d like to chat in real time, you can **schedule a call with me. Or send me an email at allie@ooux.com.**

If you’re looking to explore OOUX on your own first, here is a great free resource to dip your toes into the world of OOUX and the ORCA process: **https://www.ooux.com/uxlevelup**