Faith habits that the whole family can keep

Families who want a faith-centered home struggle to keep shared spiritual habits alive between busy schedules and competing responsibilities. Most tools are built for one person, not for a household with parents, kids, and different life stages.

Remain brings personal and family routines into one calm app: a daily verse and chapter, guided prayer for each family member, morning and evening routines, acts of kindness, and family notes.

My role

Lead designer. I ran Discovery, the logo and identity, the UI, Maze testing with 14 people, and the iteration that followed.

Team

I worked with the client from kickoff through the findings and the iteration recommendations.

Designing for a household, not a user

Parents want structure without planning everything; kids want short, clear tasks they can feel proud of.

Rooted, growing, at home

I designed the logo around one idea: the letter R grown into a tree, for identity and growth. Green, olive, and earth brown keep it organic and calm, and DM Serif Display gives it warmth. The tagline: "It Starts At Home".

Personal time and family time, side by side

A simple switch between Personal and Family on the home screen keeps both experiences in one place, and each routine is broken into small steps with examples.

Easy to love, harder to navigate than it looked

I ran an unmoderated prototype test in Maze with 14 participants: a free exploration, 5 tasks (morning, evening, and family routines, adding a family member, and finding past family notes), and a short survey on value, usability, and pricing.

What the behavior data showed

Turning friction into the next version

I recommended three improvements to the client: explain in onboarding how daily actions make the plants on the home screen grow, rework the evening routine and Acts of Kindness with step-by-step guidance and a confirmation on completion, and add instructions to find a different Bible chapter.

What this project taught me

Remain is the project where I owned the full loop, from Discovery to testing and back into design. The biggest lesson: what people say and what they do are two different datasets. A 4.9/5 ease score sat on top of 88% misclicks, and only the behavior data showed where to fix.

Quoting a load shouldn't take five tools

To quote a single load, the sales team jumped between an outdated TMS, Outlook, spreadsheets, and load boards. Past rates were hard to reuse, a unit mix-up (8'6" vs 8.6) could turn into a costly wide-load error, and turning a quote into a signed, paid order took days of back-and-forth.

The brokerage needed a sales-first platform: quote fast, send from the platform, and let the client convert, sign, and pay online, with the order moving to Operations automatically.

My role

Discovery lead and product designer: heuristic evaluation of the current TMS, the MVP re-scope, and high-fidelity UI annotated for engineering.

Team

I led Discovery with the client. The build team received screens annotated with each field's data source.

Outcome: in internal use. A sales-first MVP, re-scoped around quotes and orders, so the sales team can quote, send, and let the client sign and pay without five separate tools.

Starting from how sales actually works

What the heuristic evaluation found

A sales-first MVP

Must have

Later

Cutting to what sales needs on day one

After the kickoff, we re-scoped the MVP around the sales team: a sales-first dashboard, quotes, and orders, with Operations and Admin views moved to later phases. Every screen was annotated with its data source, so the build team knew exactly where each field came from.

Removing the expensive mistakes

What this project taught me

Leading this Discovery reminded me that the fastest way to a useful MVP is a hard re-scope: one team, one job, done well, with everything else on a clear roadmap.

Booking for someone else shouldn't take a group chat

When you book a flight for a partner, a family member, or an executive, the decision depends on two calendars, preferences, and real-world constraints. A simple purchase turns into back-and-forth texts, screenshots, and guesswork, with delays and avoidable mistakes.

Align connects the booker and the traveler: it checks shared availability, recommends flights with clear tradeoffs, keeps the budget in view, and moves from planning to booking in one flow.

My role

Discovery lead and UX/UI designer: wireframes, high-fidelity UI, and a clickable prototype, worked through with the client.

Outcome: in development. About 23 screens, from calendar matching and AI flight recommendations to traveler approval before anything is booked.

Three people who book, and one who has to show up

Daniel wants to know which flight works for both people and book it. Emily wants the flight to fit her classes and exams, and to understand why it was chosen. Olivia books for a CEO across calendars and time zones, and needs speed without mistakes.

What the journeys showed

An MVP built around one decision

Must have

Planned for V2

The outcome: a mobile app of about 23 screens focused on trip setup, calendar availability, AI flight suggestions, approvals, bookings, and payment.

Structure first, then personality

I designed the wireframes in grayscale to settle structure and flow with the client, then carried the same layouts into a calm slate-blue UI.

From an invite to a confirmed booking

Invite and match schedules

Choose, review, book

Designing for trust between two people

What this project taught me

Align is a scheduling problem disguised as a travel app. Taking it from Discovery to prototype showed me that the hardest part of shared decisions is trust: privacy you can see, reasons you can read, and a clear moment where the other person says yes.

The problem worth solving

Relapse rates among addiction recovery patients remain critically high, not because treatment fails, but because support drops off the moment patients leave the clinic.

SerenityMate addresses both sides of this gap: a mobile app that keeps patients supported between sessions, and a web-based management platform for healthcare professionals.

My role

I did the research, brand, UX/UI, and prototype for this master's thesis at ESDesign.

Starting with the people, not the product

Methods

Key findings

Four people, two products

Research and personas were produced in Spanish with patients and clinicians in Mexico.

From structure to high-fidelity

Over 70 wireframes covering both the mobile app and management dashboard, prioritizing intuitive navigation and frictionless access.

Brand

Mobile app

Clinic platform

Turning research into product decisions

Key decisions

What this project taught me

SerenityMate is my master's thesis project (ESDesign). It was one of the most complex end-to-end projects I've taken on, spanning field research at a rehab clinic, brand creation, two product surfaces, and one design system shared by the app and the clinic dashboard. It reinforced that the most impactful UX work happens at the intersection of deep user empathy and strategic thinking.

Making AI trading signals readable

Market Machines tracks algorithmic sentiment in the stock market with its own AI models. The client needed a mobile app that let traders follow those models for the companies they care about and act on buy and sell signals with more confidence.

Trades happen outside the app. Market Machines is the decision-support layer, so every screen had to make a model's signal, and how sure it is, easy to read at a glance.

My role

Discovery and UX/UI: client discovery, benchmarking, personas, the sitemap, and the high-fidelity UI.

Outcome: the interface makes a signal readable before anyone acts on it, with a confidence meter, explanations in context, and test-before-launch.

Defining the product before designing it

What the benchmark told us

An active trader first, a new investor next

Daniel trades daily and wants data-backed signals to cut emotional, impulsive trades. Laura wants to start trading without feeling overwhelmed, which pointed to the educational features we parked for V2.

A focused MVP, with a clear V2

Must have

Could have

Planned for V2

From a watchlist to programs

In the UI phase the watchlist grew into Programs: the user picks a Market Machines model, chooses the equities to follow, and gets that model's signals for each one. A dark, high-contrast interface keeps charts and signal colors legible.

Test before launching

Onboarding and alerts

Designing for trust in an AI product

What this project taught me

Designing for AI in finance taught me that trust isn't a tone, it's a structural property of the interface: showing confidence, explaining terms in place, and letting people test before they commit.

Finding water storage shouldn't take a week of phone calls

Accessing water storage today is fragmented. People who need a tank for a season, a project, or an emergency reserve jump between scattered listings, forums, and providers they can't verify. On the other side, asset owners have unused capacity and no simple way to show it.

Water Storage Hub brings both sides into one place, with real availability, clear specs, and verified owners.

My role

Solo product designer, from Discovery through dev handoff.

Team

I owned the whole project on my own: Discovery, prioritization, sitemaps, user journeys, the UX/UI for every role, and the handoff to development. There was no other designer.

Three people, one shared problem: trust

The product serves three user types with very different goals, so I defined what each of them has to get done before thinking about screens.

Primary persona

Laura manages dozens of tanks and reservoirs for a regional utility in Phoenix. Her records live in outdated systems and messy spreadsheets, and she loses hours verifying data she can't fully trust. She needs a modern tool that saves time and makes her assets easy to find.

Built for traders and regulators, not for people who need a tank

I compared three players in the water space on navigation and UI, and on content and messaging. Each one is solid at what it does, but none of them helps someone simply find and book storage.

What the first release can't live without

I sorted every feature by user type into must haves and could haves. Must haves are the foundation of the MVP; could haves add value and can land in a mid term update.

Where each journey breaks, and how to fix it

I mapped the before, during, and after of each role to find the emotional low points. Those dips turned directly into design requirements.

About 25 screens across three platforms

Each role got its own sitemap, with the tasks and purpose of every screen next to it. The owner platform carries most of the complexity (13 screens), followed by the client (7) and the admin (5). Mapping the system first let me scope the MVP honestly before designing a single screen.

Three roles, one clear path each

Client

Asset owner

Admin

Designing for trust without adding friction

Mobile where clients need it, desktop where the work happens

The product is responsive. Client flows were designed for web and mobile, because clients often search on the go or from a job site. Owner and admin platforms are desktop only, an MVP decision: listing assets, managing availability, and reviewing verifications are focused, data heavy tasks that people do at a desk, and one breakpoint kept the scope realistic.

Designed and handed off

The full MVP design was handed off to development and has not been built yet. The could haves, like favorites, an availability calendar, analytics for owners, and stronger verification with video tours, are ready for the first update once the MVP is validated with real users.

What this project taught me

Owning a product from Discovery to handoff on my own taught me that scope is a design decision. Choosing what not to build, like payments or a mobile owner app, is what made the core experience clear enough to ship.