About | Work | Writing | Podcasts | Music | Contact

Bryan McCarty

As one of the first two product managers on Jack Henry's Banno digital banking platform, I built the PM practice, ran the user research, prototyped Banno Conversations, and shipped it. Banno is now the Jack Henry Platform, the company's flagship product suite, serving 1,000+ financial institutions and 15.5M users.

• LinkedIn
• GitHub
• Medium
• Spotify

About

Hi 👋 I'm Bryan.I've spent 15 years in B2B fintech, mostly at the seam between product and marketing. I've been the PM writing requirements and running user interviews, and I've been the marketer crafting stories around what got built. Doing both makes me better at each.Some of what that's looked like: building Jack Henry's product management and user research practice as one of the first two PMs on Banno, now the Jack Henry Platform and the company's flagship product suite. Prototyping and shipping Banno Conversations, still a core feature today. Starting a customer roadmap forum that still runs monthly with 400+ attendees, 10 years later. Founding marketer at Moov, where I also produced the first two fintech_devcon conferences. First product marketing hire at Hummingbird. Head of Product at Orum through the Stripe acquisition. Most recently, re-platforming Lead Bank's API Docs from vision through launch.Outside of work, you'll usually find me trail running, training for marathons, spending time with my family, listening to hardcore music, or living the straight edge lifestyle that has been part of my life since I was 16.If you're building something interesting, or want to talk product, fintech, trail running, or hardcore, I'd love to connect.

Case studies

Banno Conversations — the first authenticated chat in digital banking
Jack Henry / Banno · 2015–2017

Community banks and credit unions had built their reputations on knowing people by name. The branch was where that happened. But as accountholders moved to online and mobile banking, that relationship had nowhere to go. The chat tools available at the time made it worse: they pushed users out to a separate experience and made them authenticate a second time, so the moment someone needed help was the moment the product handed them a hassle.The hypothesis was simple. You're already authenticated inside digital banking. Why not chat right there? And why shouldn't it feel like texting a person, rather than filing a support ticket? Typing indicators, emoji reactions, the ability to attach a transaction for context, upload a document, and see the actual name and photo of the banker on the other side. Showing a real employee's face and name was a genuinely contentious idea in banking software at the time.I turned those hypotheses into clickable prototypes and put them in front of both sides of the product. Banno builds the accountholder experience and the banker experience, so testing one without the other would have told us half the story. I ran research with bank employees and with their customers, watching where each side hesitated, what felt safe, and what felt like a support queue instead of a conversation.Conversations shipped as the first authenticated chat built into digital banking. It's still a core part of the Jack Henry Platform today, now with video, screen sharing, forms, business banking, and AI-assisted responses layered on top of the original foundation.Banno Conversations → banno.com/conversations

Orum Monitor — turning a dashboard into an operations product
Orum (acquired by Stripe) · 2024–2025

Orum's platform was API-first, which served developers well and left everyone else out. Payment operations teams were signing into what we called a dashboard, but it was really just a list of transactions. The people responsible for money movement day to day had no purpose-built place to do their work.The opportunity was clear enough. The harder question was scope. There were plenty of ideas about what an operations portal could be, and the discipline was deciding what actually belonged in the first version: enough value to justify a new name and a launch moment, without waiting to build everything.I led the vision and directed the UX, made the calls on what shipped and what waited, wrote the product guides, and produced the demo videos. We packaged it as Monitor, launched it at an industry event, and kept prioritizing the backlog against it from there.Monitor became the first portal built to orchestrate payment operations rather than just report on them. Individual users and time on site both rose after launch, which was the signal we wanted: ops teams were doing their work in the product instead of checking on it.Orum Monitor → docs.orum.io (includes a 2-minute demo)

Lead Bank API Docs — treating docs as a product
Lead Bank · 2025–2026

Documentation at Lead was an afterthought. Guides got written after features shipped, by whichever PM had shipped them, which meant every page had a different voice, a different structure, and no shared sense of who it was for. Nobody thought of docs as part of the product. The site was behind a password, because leadership was embarrassed by it.I made the case that developer documentation is the product for a bank whose customers integrate by API, and that it deserved the same ownership as anything else on the roadmap. That meant getting executive buy-in for a full re-platform rather than another round of cleanup.I owned it end to end: the vision and the plan, the move to Mintlify, the information architecture, the voice and tone standards, content hierarchy, and changelog norms. Less visible but more important, I changed how the team thought about docs — from something you write after shipping to something you design alongside the thing you're shipping.At launch, leadership was comfortable enough to take the password off and make the site public. We started tracking usage for the first time. Partners began treating the docs as the source of truth instead of opening a support ticket first. The team continues to build on the foundation I set.Lead Bank API Docs → docs.lead.bank

Select launch writing, essays, and product guides

Orum

Orum (acquired by Stripe, July 2025) — 15 product launches including Verify, Subledgers, Business Name Match, Scheduled Transfers, and the Visa Direct partnership. Orum's blog was retired after the acquisition.

Hummingbird

Moov

Aha! — product management guides

Aha! — product launch writing

Fintech essays

Product and go-to-market

Podcast appearances

Music (vocals)

Say hello

Working on an interesting problem? Hiring? Let's chat.