UX Designer · MIS Background · Systems Thinker
UX designer with a B.S. in Management Information Systems — I don't just design screens. I map the full system: people, processes, data, and the gaps where things fall apart.
"There was a messy notebook on the counter. The information was inconsistent, difficult to follow, scattered across multiple pages. My solution was simple: I created a spreadsheet."
My journey into UX began unexpectedly. After 19 years as a stay-at-home mom, I became a caregiver by chance for a patient with dementia. The first day I arrived at her house, I saw that notebook on the counter — inconsistent, difficult to follow, scattered across multiple pages. Having a background in Management Information Systems, it immediately caught my attention. I didn't see a mess. I saw a broken system.
That was my turning point. Returning to work after two decades isn't easy — I needed an upgrade. After exploring different paths, I discovered UX Design and realized it was the bridge between my interest in people and my background in systems. What I thought was forgotten turned out to be just hidden. As I worked through each project, I noticed a pattern: I naturally mapped relationships between users, service providers, and the organizations supporting them. Every time.
Through these projects I discovered that my strength lies in understanding how people, processes, and information work together — identifying where things break down, and designing solutions that improve coordination, visibility, and the overall experience. What motivates me most is the opportunity to make a meaningful impact. I am drawn to problems that affect people's daily lives. My goal is not simply to design products — it's to create solutions that reduce frustration, improve experiences, and make life a little easier for the people who rely on them.
I'm completing a UX/UI Design Bootcamp at Noble Desktop, building my portfolio in English and Spanish — both fluent, both first-class design languages.
Research synthesis, wireframes, prototyping, usability testing — grounded in what users actually need, not what stakeholders assume.
I naturally map how users, service providers, and organizations connect — and where the seams break. That's how every project starts.
I understand how data flows and how systems are built. That shapes every design decision — and lets me work fluidly with developers.
Each project is a systems problem first. A design problem second.
Patients are inviting a stranger into their home during a vulnerable moment. Trust is not a feature — it's the product.
Why do I have to wait 8 hours? A connected service ecosystem for customers, technicians, and dispatch — built from three simultaneous research tracks.
People don't want to become produce experts. They want to know what to make for dinner. One research insight that changed the entire product strategy.
"Why do I have to wait 8 hours for the cable technician to show up?"
Telecom service appointments involve multiple stakeholders operating with limited visibility and disconnected information. Customers lack updates. Technicians carry administrative burden. Dispatch teams react instead of coordinate. The experience fails at every seam.
Each stakeholder feels a different failure — the same root cause: disconnected information.
Receives an 8-hour window with no visibility into arrival time and no proactive updates. Uncertainty drives repeat support calls.
"I've been waiting all day. Can anyone tell me where they are?"
Receives incomplete job details, then completes all documentation from memory at end of shift — producing inaccurate reports.
"By the end of the day I can barely remember what I used at the first job."
Manages operations across multiple disconnected systems, reacting to delays without real-time data.
"We only find out there's a delay when the customer calls to complain."
Three simultaneous surveys — customers, technicians, and dispatch — designed to capture each stakeholder's experience independently, then synthesize across all three.
Real-time tracking and proactive status updates that eliminate the support call.
In-field documentation that ends end-of-day memory-based logging.
Materials auto-logged at point of use — not reconstructed from notes later.
Real-time operational visibility — no more reactive coordination.
One system that keeps all three stakeholders on the same status simultaneously.
Structured data flows replace manual processes across the full service journey.
* Projected impact goals. Validation pending usability testing and pilot data.
Secondary research complete across telecommunications, field service operations, and competitive platforms. Three primary research surveys distributed across customer, technician, and dispatch audiences. Next: survey analysis → persona development → journey maps → service blueprint → wireframes → prototype → usability testing.
Most UX work optimizes the visible layer. I start one level upstream — at the system that produces the experience — and work outward from there.
I define the actual problem before I sketch anything. That means mapping the system — actors, data flows, constraints — before touching a wireframe.
Frontstage, backstage, and the data layer underneath. My MIS background means I think in systems naturally — not as a technique, but as a default.
I read data clearly — and I know when qualitative insight tells you what numbers can't. I use both, and I flag when a source is weak.
English and Spanish — not as a translation layer but as a first-class design constraint that shapes the whole system from the start.
Available for UX design roles and product collaborations — especially in healthcare, operations, and complex service systems where the design problem runs deeper than the UI.