Skip to main content

    Lead UX Designer & Researcher

    I make complex systems work better for the people who depend on them.

    I’m Elise, a UX designer and researcher who leads discovery, shapes product decisions, and helps teams turn complex problems into clearer experiences.

    It usually starts with me asking, “Wait, why do we do it that way?”

    First, I get close
    to the work.

    Curiosity, up close
    On the ground at Alaska Airlines

    The problem isn’t where everyone thinks it is.

    A confusing screen might actually be a broken handoff. A slow process might be asking someone to do work the technology could handle. And a seemingly simple fix might create a whole new problem somewhere else.

    I love figuring out those connections—and helping teams decide what to do about them.

    Illustration: a screen problem traced to its causesAt the top, a screen shows a confusing message — the symptom everyone sees. Lines run below the surface to a customer, an agent, a separate tool and a back-office system. The handoff between the agent and the back-office system is circled as the underlying cause.What everyone seesSomething went wrong.“The screenis confusing.”UnderneathCustomerin a hurryAgentworks around itThe Toolanother screenBack-office systemseparate record← broken handoffthe real problem
    Illustrative composite of a pattern I see often — not a specific project or product.

    Selected work

    Four projects, four ways I move work forward.

    Starting research nobody asked for, designing AI that agents stay in charge of, teaching other designers, and building screens for a busy cargo counter.

    1. Discovery I proposed · evidence to recommendation

      1. 7 interviews
      2. 27 findings
      3. 9 affinities
      4. 5 recommendations

      1 · Initiative & strategy

      Atlas 2.0 · For airline teams that take and support payments

      Can every team see what happened to the same payment?

      I independently proposed and led stakeholder discovery across payment teams, then turned seven formal interviews and 27 findings into five recommendations.

      Research scope7 formal interviews · 27 findings · 5 recommendations

      Role: Initiated and led stakeholder discovery

      • Payments
      • Research
      See the five recommendations and their evidence
    2. Observed task time · same task segment

      Without
      13:29
      With tool
      10:05

      About 25% lower observed task time.

      2 · AI design · measured result

      CareConnect · For Customer Care agents

      What can AI take off an agent’s plate before they reply?

      I led research and designed how agents could check the AI’s analysis, edit a draft, and decide what to send.

      Verified outcome25% less time preparing a reply · 13:29 → 10:05

      Role: Senior UX Designer & Researcher

      • AI
      • Workflow
      See how agents review an AI draft
    3. Workshop flow · hands-on, not a lecture

      1. Orient
      2. Build an agent live
      3. Compare with my synthesis
      4. Q&A

      3 · Teaching & influence

      AI Enablement · For design teams learning Copilot

      What did Copilot see in the notes I’d already synthesized?

      I designed and led a workshop where we compared a Copilot agent’s affinity themes with my own Miro synthesis.

      Role: Designed and led the workshop

      • AI
      • Enablement
      See the side-by-side synthesis exercise
    4. Handoff sequence · 5 agents, 3 customers observed

      1. Desktop
      2. Customer iPad
      3. Reader
      4. Confirmation

      4 · Enterprise UI · field research

      Cargo Payment Portal · For cargo agents and customers

      The agent’s screen said complete. The customer’s iPad kept loading.

      I observed payments at Seattle Cargo Station and designed clearer signing, shared status, and recovery across the desktop, iPad, and card reader.

      Research scope5 agents + 3 customers · desktop, iPad, and reader

      Role: UX designer and field researcher

      • Payments
      • Research
      See the payment handoff across three devices

    How I work

    How I help teams move forward

    I lead mostly through influence: asking the question that reframes the problem, getting the right people in the room, and making the next decision easier to see.

    1. Spot the deeper problem

      Payment teams could each explain their own piece, but nobody could see the whole. I proposed a stakeholder discovery on my own initiative and led it.

      Atlas 2.0 · 7 formal interviews, 27 findings, 5 recommendations

      Read the Atlas 2.0 story
    2. Bring people together

      I run research with the people who own different parts of a workflow, then turn what we learn into decisions product, engineering, and operations can weigh together.

      CareConnect · Customer Care, product, engineering, and the AI team

      See how CareConnect decisions were made
    3. Make complex things usable

      I follow the work across screens, devices, and teams, then design the handoffs where it tends to break.

      Cargo Payment Portal · desktop, customer iPad, and card reader

      Follow the Cargo payment handoff
    4. Help others learn

      Before UX, I taught special education for seven years. I still teach: I designed and led a hands-on Copilot workshop where designers watched me build an agent live.

      AI Enablement · workshop for designers

      Inside the Copilot workshop
    More about me, from classroom to research

    Recommendations

    What it’s like to work with me.

    Kind words from people I’ve worked with, summarized from LinkedIn recommendations and notes from coworkers.

    Coworker commentSummary

    Ryan was impressed by Elise’s AI work and detailed prompts. Her prompt for a “what I accomplished last year” share-out taught him practical ways to improve his own prompting.

    Ryan SmithCoworkerPractical AI craft
    Coworker commentSummary

    Jacob described Elise’s AI work at Alaska as instrumental in helping both guests and the frontline, recognizing its value for customers and employees alike.

    Jacob mCoworkerGuest & frontline impact
    Coworker commentSummary

    Pablo always enjoyed Elise’s enthusiasm for learning new technologies in their meetings, highlighting the curiosity and energy she brought to shared team discussions.

    Pablo CasanovaCoworkerCuriosity in practice
    Coworker commentSummary

    Jesse enjoyed seeing the UX research and design work Elise shared in design meetings. He thanked her for openly sharing her work and said it kept him motivated and inspired.

    Jesse ErandioCoworkerSharing the process

    1 / 6

    Connect with me on LinkedIn

    I believe in showing the evidence—not just the finished screen.

    Different problems call for different kinds of research. Here’s what I studied, measured, and brought back to teams.

    Measured result · CareConnect

    ~25%

    less time preparing a reply

    Without CareConnect
    13:29
    With CareConnect
    10:05

    That’s 3:24 less in the observed post-rollout comparison. Agents checked and edited the draft before returning the reviewed reply to their case.

    Read the CareConnect case study

    Research scope

    Who and what I studied—sample sizes, not performance results.

    • 5 + 3

      Agents and customers observed across desktop, iPad, and reader.

      Cargo Payment Portal
    • 5 · 16

      Agent interviews and documented UAT scenarios.

      Receipt & Inquiry
    • 6:54

      Mean failure-to-success time across 6 controlled-study participants.

      QR Pay-by-Link
    • 7

      Stakeholder interviews synthesized into a shared research baseline.

      Atlas 2.0

    Let’s talk

    Have something interesting you’re working on?

    I love a complicated problem, a thoughtful team, and a good conversation. If you’ve got something that could use a fresh perspective, I’d love to hear about it.

    elise.ivory14@gmail.com

    For agencies: I’m happy to share detailed work samples and process documentation privately under NDA. Just reach out.

    Send a message

    Fields marked * are required. I reply within 1–2 business days.

    Please don’t include confidential customer or company information.