JTBD Interview Analysis: Jeremy Braun
This is an internal bank-employee interview about adopting and using the Autobooks Hub as a support tool, not a consumer switch story. The transcript is truncated at roughly the 6-minute mark of a 39-minute conversation.
Interview Summary
Okay, here's what I just heard, and I want to be upfront: this is not a classic demand-side switch story, and the transcript I have cuts off after about six minutes of a 39-minute conversation. So most of what would matter is missing.
What I can tell you is who Jeremy is and what situation he's in. He's a 25-year banking veteran, eight years at Midwest, working on the treasury and cash management side. He is not the buyer of Autobooks and he is not a small business customer using it. He's an internal stakeholder who got, in his own words, "thrown into it pretty late in the process." That's the most alive moment in what I have. There's real energy in his description of finding out six weeks ago that a product he assumed lived in another department, aimed at small business, was going to spill over onto his corporate treasury desk.
The story he's telling is an internal ownership-and-scope story, not a hiring story. The recurring theme is uncertainty about who owns this thing. He describes an assumption that Autobooks "really wasn't in our purview and we wouldn't really have any dealings with it," followed by the gradual realization that "there's going to be a lot of crossover" and "it's definitely going to impact us in Treasury." The addition of smart checking expanded the footprint further. His group handles the digital and business banking questions, so calls will "naturally come to us."
The Hub itself barely gets characterized before the transcript ends. What he says is that it was initially pitched as "more just a quick visual" to see which customers are in the product, but "it wasn't really a support tool of any kind." And the tension he's starting to voice right at the cutoff is that when the phone calls come, his team won't have the background or information in the app to answer them. That's the seed of a real product insight, but the transcript ends before it develops.
Bottom line: this is a usable interview about internal tool adoption and organizational readiness, but it is not a consumer JTBD switch story, and the portion I have is too short to reconstruct the full arc.
Timeline of Events
Jeremy begins his banking career in treasury/cash management/digital roles
Joins Midwest, focused on treasury services sales and support
Midwest onboards Autobooks; first customer goes live
Jeremy first hears about the Hub
Product presented to Jeremy as hands-off, living in a different department, solely a small business product outside his purview
Realization builds that there will be "a lot of crossover" with corporate treasury customers
Smart checking is added, expanding the product footprint and reinforcing that it will impact Treasury
Jeremy expects inbound phone calls his team can't easily answer without background or information in the app
Four Forces of Progress
Driving Change
Resisting Change
When I got thrown into a product late in the process that I assumed wasn't mine to deal with.
"I got kind of thrown into it pretty late in the process... I thought this was just a small business thing. How is this impacting us?" He was learning on the fly, catching up on decisions already made.
When the product's scope expanded and started crossing over into my corporate treasury customers.
"It's definitely going to touch our... larger corporate customer treasury side... there's going to be a lot of crossover."
When smart checking got added and the footprint grew even further.
"Now with the smart checking and things like that... it's expanded even more."
When I know the phone calls are coming to my group and we won't have the background to answer them.
His group handles "the majority of our business digital type questions," so "they'll naturally come to us," and right at the cutoff he raises the worry of not having "any background on any information in your app."
When there is uncertainty about who actually owns this product.
"A period of uncertainty... around ownership. And I think there was just some hope maybe that it didn't have to live within our area."
Worry that his team will be fielding questions the Hub can't help them answer.
The concern forming right at the transcript's end is that if calls come in "and we didn't have any background on any information in your app," his group is exposed. This is a pre-adoption worry about whether the tool will actually support his team's job.
Forces Synthesis
This is an imposed-adoption story, not a voluntary switch, so the four-forces balance does not resolve into a clean tipping point. The dominant force is push, and it is external and organizational: scope creep from a small business product into corporate treasury, a late and messy handoff, ownership ambiguity, and the certainty of inbound customer calls his team must handle. The one anxiety that surfaces, whether the Hub gives his team enough information to answer those calls, is the analytically important thread, but the transcript ends just as he begins to voice it. There is no pull and no habit in what was captured, which is consistent with someone who did not go shopping and was handed a decision made above him.
Functional, Social, and Emotional Requirements
Functional
1 requirement
- The Hub needs to be more than "a quick visual" of which customers are enrolled. Jeremy signals it must function as a support tool that surfaces the background and account information his team needs to answer inbound questions. Right now he characterizes it as visibility without support.
Social
1 requirement
- Ownership and hand-offs across groups are central. Small business bankers and branch staff will surface questions they cannot answer, which flow to Jeremy's treasury group. The tool sits at an organizational seam between departments, and clarity about who owns and supports it matters as much as the tool itself.
Emotional
1 requirement
- Jeremy needs to feel prepared and not caught flat-footed. The felt experience of being "thrown into it late," "learning on the fly," and bracing for calls he cannot answer points to a need for confidence and readiness before customer contact starts.
Interview Quality Assessment
Was this the right person
Partially. Jeremy is a knowledgeable internal stakeholder with deep banking tenure and a real perspective on how the Hub affects treasury operations. But he is not a buyer, not a chooser, and not an end consumer of the product, so this is not a demand-side switch interview in the JTBD sense. It is useful as internal-readiness and tool-support research, not as a hiring story.
Emotional energy
There was genuine energy in one place: the frustration and slight defensiveness of being pulled in late ("I kind of jumped into it a little bit late... Apologize for that... learning on the fly"). That is signal about organizational friction. Most of the rest is measured and somewhat vague.
Did the interviewer get to specific moments
Only partially, and the interviewer was working toward it, anchoring on "six weeks ago" and "the first time you heard about the Hub." But the transcript ends before the interviewer could get Jeremy into a specific scene. We never get a concrete moment of him using the Hub or fielding an actual call.
Areas where follow-up could have uncovered more
None
Overall
The captured portion is too short (roughly 6 minutes of 39) to support a full analysis, and even a complete version would be an internal-adoption interview rather than a consumer switch story. It is worth keeping as organizational-readiness input, but it should not be treated as a demand-side JTBD case study. The most valuable move is to recover the full recording, because the thread about the Hub failing as a support tool starts precisely where this transcript cuts off.
Product & Business Opportunities
Make the Hub a genuine support tool, not just a roster
Jeremy's sharpest observation is that the Hub was framed as "a quick visual" to see enrolled customers but "wasn't really a support tool of any kind." Internal staff who field crossover questions need enough account and background information in the app to actually resolve those questions. This is the single most concrete signal in the interview and worth validating across other treasury and support staff.
Address the cross-department handoff and ownership gap
The product was scoped as small business only and lived in another group, but it bled into corporate treasury without clear ownership. There is an opportunity to provide implementation guidance that maps out which internal teams will get which questions once smart checking and treasury crossover kick in, so banks do not experience the "period of uncertainty around ownership" Jeremy described.
Prepare downstream support teams before go-live
Jeremy was "thrown into it pretty late." The pattern of a support-adjacent group learning about a product on the fly, after customers are already live, is a preventable failure. Earlier onboarding and enablement for treasury/digital support teams could reduce the readiness gap.
Anticipate scope expansion from small business into corporate treasury
The addition of smart checking widened the footprint. Positioning and rollout materials should set expectations that this product does not stay contained to small business banking, because larger corporate treasury customers and their support teams will be touched.
Transcript Uncertainties
- The transcript is truncated. It ends mid-sentence around 6:15 of a 39m 32s recording. The large majority of the conversation is missing, including any discussion of actual Hub usage, specific customer interactions, and how the support-tool concern resolved.
- "Men West" vs "Midwest." The auto-transcript renders the bank name inconsistently ("Men West," "Midwest"). I have used "Midwest" but this should be confirmed.
- A third participant, Charlie Blaesser, appears once ("Do.") with no substantive contribution in the captured portion. Their role is unclear.
- "peer sales" / "front... dashboard" around 0:58 to 1:34 is garbled and Jeremy's description of seeing "both sides" is hard to parse precisely.
- Timing of smart checking's addition is not pinned to a date; Jeremy references it as a more recent expansion but the sequence relative to the six-week mark is not explicit.