JAKE REDMOND
PRODUCT DESIGNER
My background is in technical production, business systems, and complex product delivery—not graphic arts.
I approach product design as the discipline of translating dense business logic into interfaces that users can navigate safely, and engineers can implement without guessing.
// Scale Is Not Created By Polish
My approach to UX was shaped in regulated, high-stakes environments where product behavior cannot be vague.
As a UX Design Lead for U.S. Online Banking at TD Bank, I designed secure, compliant digital banking flows serving 10M+ users. In that environment, success is not determined by surface-level aesthetics. It is determined by clear permissions, predictable states, visible recovery paths, validation rules, and product behavior that can survive strict engineering and compliance review.
I bring that exact same standard to scaling B2B SaaS, Fintech, and legacy ERP modernization.
// Logic before pixels
I do not start with screens. I start with the rules underneath them.
A product flow is only safe to build when the critical system behavior is mapped:
→ What happens when the API fails or times out?
→ Who has the systemic authority to approve, reverse, or retry the action?
→ What state owns the engineering handoff?
→ What user behavior is strictly forbidden by the backend?
→ What edge cases must development account for before the UI loads?
I define that behavior before implementation begins. That work becomes implementation-ready UX: defined states, constraints, failure paths, and permission boundaries that make complex workflows faster to build and safer to ship.
// The Right Fit
I am built for teams where undefined UX requirements 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 is stalled waiting on complete, buildable UX requirements.
UI components regularly break when populated with real-world data density.
You are modernizing a legacy system (like an AS-400 or old ERP) and need the logic translated correctly.
We are not a fit if:
You only need a visual UI/brand refresh.
Your product is a simple, low-risk consumer application.
You need pitch-deck screens without system behavior mapped underneath them.
If your engineering team is stalled on undefined edge cases, that's a handoff problem. Let's fix it.