Innovation Unpacked | Mike Boysen
Oct 4, 2026 · 17 min · 10 segments
You absolutely do not need Venture Proof. You can build the strategy yourself. Or you can hire a consulting firm the way you always have. You keep the costs you know. You keep the success rates you…
Her job is to reconcile multi-rail transaction exceptions before the market clearing window shuts at the end of the day.
Every minute she spends outside her primary core banking ledger isn't an engagement win for you.
In jobs to be done, the functional job is completely stable regardless of the technology you use to solve it.
When you change the location of your solution in the customer's environment, you aren't trying to capture their eyeballs.
You're taking your core resolution engine and embedding it directly into the surface they already inhabit.
Product teams assume that because they spent 12 months building a product, the end user wants to live inside it.
They add notification bells, custom filtering tables, export to spreadsheet buttons, and automated email alerts that ping the customer saying, you have an unresolved exception, log into view.
The user opens the email, sighs, copies the error reference number, opens a new tab, waits for a single sign-on to authenticate, navigates three menu tiers, pastes the reference number, clicks approve, and then immediately tabs back to their actual job.
Ban terms like stickiness, portal engagement, single pane of glass, and driving daily active usage.
Her job is to reconcile multi-rail transaction exceptions before the market clearing window shuts at the end of the day.
Every minute she spends outside her primary core banking ledger isn't an engagement win for you.
In jobs to be done, the functional job is completely stable regardless of the technology you use to solve it.
When you change the location of your solution in the customer's environment, you aren't trying to capture their eyeballs.
You're taking your core resolution engine and embedding it directly into the surface they already inhabit.
Product teams assume that because they spent 12 months building a product, the end user wants to live inside it.
They add notification bells, custom filtering tables, export to spreadsheet buttons, and automated email alerts that ping the customer saying, you have an unresolved exception, log into view.
The user opens the email, sighs, copies the error reference number, opens a new tab, waits for a single sign-on to authenticate, navigates three menu tiers, pastes the reference number, clicks approve, and then immediately tabs back to their actual job.
Ban terms like stickiness, portal engagement, single pane of glass, and driving daily active usage.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.