Secret recipe: ooux

SaaS product startups, imagine this...

After just one day, you walk away with...

Clarity and team alignment on the architecture of your product

Strategy of how you need to structure a feature

Basic sketches of your wireframes that you can quickly prototype and test

A visual map of all the parts of your product - encompassing needs for every department

No, it's not a get-rich-quick pyramid scheme or snake oil - It's called OOUX (Object-Oriented User Experience)

It a phase that sits neatly between user investigation and design part of the product process.

OOUX hones in on your customer's mental model, and makes sure the products you make actually follow.

Really just one day?

One day is enough to get a taste of your product or a specific feature mapped out.

Highly recommended to go deeper beyond the one day, but it's enough to cover the fundamental building blocks of your product. You can see for yourself!

I've crafted a "UX in a Bottle" workshop specifically for early-stage start-ups that have limited resources and can't bring on a UX / Product Designer quite yet.

No fluff, no BS, very hands-on workshop for your whole team to dig into your product.

Your whole team can come! This is not just for founders, or developers, or product people - it's actually better if you have all kinds of teammates there. Yes, even sales and marketing can come too.

Roll up your sleeves, we need your undivided attention for the entirety of the workshop to make sure it's effective - no multi-tasking!

"UX in a Bottle" Workshop for Early-Stage startups

Perfect for teams with bite-size budgets that want to make sure their products are intuitive and chaos-free - even without hiring a UX designer
• 4 hours workshop via Zoom
(In-person 120 miles radius to Tulsa, OK)* with breaks built in
• Up to 12 participants

• Hands-on activities to apply the basics of OOUX to a real aspect of your product
• OOUX Fundamentals that you'll be able to apply to all parts of your product
• Real-world examples
• Object map - a new diagram to keep everyone on the same page

*Gas reimbursement required

OOUX Fundamentals

This is a full-day workshop for teams that want to a more-robust look at their product or specific feature. We go deeper than the half-day workshop.
• + everything from the "UX in a Bottle" Workshop
• 7 hours workshop (with breaks)
• Navigation map - Information Architecture
• Object guide AKA bible of your product

Product Design Partner

Walk away with the whole architecture of your product designed out. Whether it's a new feature, or the MVP - I'll be your product design partner. I'll use OOUX as a baseline to collect requirements and work alongside you to map out how your product will work.
• + everything from the day workshops
• Multiple week sprints with each day dedicated to honing in on the core of your product (Can be spread out over time)
• I'll do extensive pre-work of your domain
• User research
• User flows
• Journey Map
• Wireframes
• User Testing
• Development requirements and documentation

what if we want more than just one day?

I love working with clients on projects doing really in-depth OOUX and UX strategy, as well as helping with the design aspects like wireframes, user flows, user testing, and the rest of the UX process.

If your team wants to dig deeper and end up with an extensive look into your product, happy to help!

We can do a workshop series, or on-going collaboration. Or if you just need a consistent UX partner, I'm your gal.

What are the steps of ooux?

Let's use an example of a tool that manages soccer games.


Check out my talk at a dev conference about ooux:

tell me more about ooux...

Object-oriented UX leans into the fact that humans think in objects.

Our interactions, goals, and daily lives are centered around objects. When people visit a supermarket, their thoughts revolve around specific items like "Eggs" and "Milk," not abstract processes like "Check-out" or "Compare prices."

This is the key step that other UX designers and agencies miss.

The best products and experiences SHOULD BE CONNECTED and not siloed.

This gives you more accurate scoping and requirements from the start, and let's all your stakeholders have a voice that connects priorities instead of competing against each other.

We bring all your stakeholders into a few interactive workshop to define and prioritize these requirements.

Investing this time at the start will save you hours and hours of rework, miscommunciations, and changes in requirements - and overall decreasing risks of burnout from a chaotic project.

In contrast, traditional UX design often involves separate teams tackling different aspects, such as designing the stocking process and creating the check-out, without sufficient discussion of potential overlaps. This approach can lead to disjointed user experiences.

OOUX engages the left side of the brain, systematically breaking down data.

Unlike the common practice of software engineers reverse engineering designs, OOUX involves collaboration between designers, developers, and non-technical stakeholders. This collaborative effort aims to define the necessary data for the back-end and content management system (CRM). By working together, we determine what information must be collected, stored, and represented.

The attached functional requirements document is a proactive step. It serves as a guide for developers before the design phase begins, preventing potential roadblocks and saving valuable time.

Why do non-technical people need to think about data-models?

Imagine you had customers signing up for your video platform.

  • Sales wants to know their email to keep selling future products
  • Content creators want to know what kind of videos they are interested in
  • Marketing wants to know how they found out about the app so they can expand their campaigns
  • Leadership wants to know the user's priorities on the app

Those are all different requirements that each department needs.