JAKE REDMOND

Senior PRODUCT DESIGNER

I’m a Senior Product Designer available for short-term contract work across enterprise SaaS, fintech, AI-enabled workflows, and legacy modernization.

I help teams untangle complex workflows, clarify product decisions, and get features ready for engineering.

I work well as embedded senior capacity on active projects or as agency overflow when a team needs experienced support quickly.

My approach is shaped by high-stakes products where roles, permissions, integrations, recovery paths, and system behavior need to remain clear under real-world conditions.

View Full resume

DISCUSS A PROJECT

// Scale Is Not Created By Polish

My approach to UX has been shaped in highly regulated, high-stakes environments where system behavior cannot be vague. As a UX Design Lead for U.S. Online Banking at TD Bank, I architected secure, compliant digital banking flows serving 10M+ active users.

In that environment, products scale when behavior remains consistent across users, permissions, exceptions, integrations, and recovery paths.

I bring that exact same operational standard to scaling B2B SaaS, complex fintech platforms, legacy ERP modernization, and agentic AI systems.

// AI Systems & Workflow Reliability

When AI becomes part of a workflow, product behavior becomes harder to predict.

I help teams answer the questions that determine whether an AI feature can operate safely in production:

[01] What happens when the model output is incorrect or confidence is low?

[02] What happens when required data is missing from the system?

[03] When should a human explicitly intervene?

[04] How should users recover when automation fails?

By defining those behaviors before implementation begins, teams can introduce AI into production workflows without creating operational chaos.

// System Behavior Defined

Before development begins, teams need clear definitions for how AI behaves when real-world conditions introduce uncertainty. Engineering receives:

→ Failure and timeout states

→ Human escalation paths

→ Permission and approval boundaries

→ Data validation requirements

→ Recovery and retry logic

// Logic before pixels

// Operating Framework

        [01]
      
Align Stakeholders & Map Constraints
Before I open Figma, I facilitate alignment between product, engineering, and business leaders to map the legacy architecture and define the exact outcomes required.

        [02]
      
Untangle Edge Cases & System Behavior
I work directly with engineering and compliance teams to untangle ambiguous logic, collaboratively documenting the "unhappy paths" so we don't discover them mid-sprint.

        [03]
      
Architect for Human Cognition
I translate those rigid system constraints into a progressive, human-readable interface—protecting the user from database complexity and drastically reducing cognitive load.

        [04]
      
De-Risk Engineering Implementation
I deliver state-machine logic alongside the UI, acting as a reliable bridge between design intent and engineering execution to ensure zero translation failure.

// The Right Fit

I am built for product teams where undefined UX requirements or complex workflows are bottlenecking development.

We are likely a fit if:

Senior developers are playing product manager during implementation to fill in missing UX logic.
Your product depends on complex permissions, heavy data tables, or strict edge states.
Engineering velocity is stalled waiting on complete, buildable UX requirements.
UI components regularly break down when populated with real-world data density.
You are modernizing a legacy system (like an AS-400 or legacy ERP) and need the application logic translated correctly into modern UI.

Initiate Sync