Business or Enterprise or Family

The following will be imprecise because every situation is totally different.

Conference attendees retrieve presentations on your enterprise website (Note: this is a demo site), which might include…

  1. An image to trigger the memory.

  2. A short synopsis, similar to CliffsNotes, for focus.

  3. Presenter’s prompt (optional) with references, resources, and visual files.

  4. Default presentation: Importing an .onda file into Replay enables anyone with the link to hear the original presentation, follow the audio with Karaoke-style highlighting, and access an index. The index maps to the transcript text, then back to the audio recording.

  • SYNOPSIS

    “The Fist 👊: Building High-Performing Product Teams,”

    A 15-year product veteran and former athletic coach argues that the most impactful framework in product management isn't a backlog methodology — it's team culture. Drawing on Coach K's five-value "fist" model (Communication, Trust, Care, Collective Responsibility, Pride), the speaker shows how he rescued a 22-engineer team with zero shipped product by fixing the human dynamics first. The result: a January launch, daily release rhythm, 400K active users, six product lines, and $100M revenue over four years.

  • “The Fist 👊: Building High-Performing Product Teams,”

    CLIFF'S NOTES

    The Problem He Walked Into

    • Internal startup, blank check, 22 engineers, 8 months in — nothing working

    • Lots of work in progress, zero done; business and tech in open conflict

    • Root cause: broken team dynamics, not broken backlog

    Coach K's AVIS Fist (the fix)

    • Communication — look each other in the eye, tell the truth, narrow the knowledge gap; both sender AND receiver have a job

    • Trust — I believe your word instantly

    • Care — I've got your back, don't hesitate

    • Collective Responsibility — we win and lose together; no finger-pointing breaks the fist

    • Pride — missionaries not mercenaries; everyone deserves to belong to something bigger than themselves

    Product Trinity (Marty Cagan)

    • Design, Engineering, Product — no single function wins alone

    • Handoff culture kills products; overlapping Venn diagram is the goal

    Three Types of Thinking (Sherris Doshi)

    • Product thinking → impact

    • Project thinking → execution

    • Political thinking → optics

    • Great teams prioritize in that order

    Energy Givers vs. Energy Takers

    • Every interaction either fills or drains someone's bucket

    • 9/10 people are more productive around positive people

    • Replace SCAR (uncertainty/fear) with certainty: "we don't know the answer yet, but we find out on this date"

    • Swarming: when something's critical, everyone helps regardless of role

    How to Actually Do This as a PM

    • You are the default leader — set the tone, others follow

    • Don't announce the framework on day one; model it first, build trust, then have the explicit conversation

    • Use the Golden Mean (Aristotle): find the right amount — too much communication is also a failure

    • Always explain the why; engineers who can't articulate the impact of their work are disconnected

    The Outcome

    • January launch after a near-total collapse

    • Daily releases, rhythm and flow

    • 400K active users, 6 product lines, $100M revenue over 4 years

    Watch-out

    • A healthy product team can still clash with a politically driven organization — cultural awareness outside your team matters as much as inside it

  • Structure the Output

    The organization or enterprise can generate any number of outputs here. Ian could provide a link to his deck or other supporting references or documents.

    1. A conversation happens. Replay captures it.

    2. The recording becomes a transcript — unfiltered, unedited, exactly what was said. (automatically)

    3. The transcript is a map of the audio file. (automatically)

    4. The karaoke helps you follow along with the audio. (automatically)

    5. The index maps the transcript. (automatically)

    The user tells the AI to generate a markdown prompt file that structures the conversation for them — private, personal, human-readable, no black box. (your instruction). [See Examples below]

    Replay records and transcribes in up to 99 languages, returning native text. A conversation in Spanish stays in Spanish. A conversation in Mandarin stays in Mandarin. The transcript is always in the language and text alphabet in which it was spoken.

    When a different audience needs it, Replay translates — from any of those 99 languages to any other. The auto shop owner in Texas gets the client summary in English. The crew gets their work order in Spanish or can translate the transcript into Spanish. Same conversation. Same recording. Both audiences served.

    One recording. One transcript. Unlimited outputs.

    The prompt is yours. Replay doesn't own it, doesn't see it, doesn't store it. You write it once, save it on your own machine, and it works every time.

    This is not AI deciding what matters. This is you deciding what matters, and AI doing the formatting work.

    The audio is always there. The transcript is always there. The documents are generated on demand. Nothing is hidden, nothing is automatic, nothing happens without your instruction.

    That is the whole system.

  • Examples of markdown scripts.

    Conference Talk — Cliff's Notes"Summarize this presentation for a professional audience. Extract the three most actionable takeaways. Use plain language. No bullet point longer than two lines."

    Auto Shop — Work Order"You are a service writer. Extract every repair discussed, parts mentioned, and any customer authorization given. Format as a work order. Flag anything that was agreed to verbally but needs written sign-off."

    Family Meeting — Action List"This is a personal conversation between family members. Extract every commitment made, every decision reached, and every open question still unresolved. Format as a simple to-do list with owner and due date where mentioned."

    These prompt files are created by Claude, ChatGPT, Gemini — or written by hand. Any AI, any text editor, any device. Copy and paste. Once written, they belong to you.

    The same transcript run through a different prompt produces a completely different document:

    Prompt:

    Output Conference organizer Synopsis + Cliff's Notes for the website

    Auto shop service writer:

    Work order with agreed repairs

    Shop owner:

    Client conversation record, liability documentation

    Finance manager:

    Billable items and authorizations

    Spouses: What we talked about, what we agreed to, who does what, explain like I’m 5

    One recording. One transcript. Unlimited outputs.

    The prompt is yours. Replay doesn't own it, doesn't see it, doesn't store it. You write it once, save it on your own machine, and it works every time.

    This is not AI deciding what matters. This is you deciding what matters, and AI doing the formatting work.

To listen to presentation: Download Replay by ONDA

  • SYNOPSIS

    would go here

  • Would go here

To listen to presentation: Download Replay by ONDA


Replay is really different, in a very human way.

It helps you find what matters faster, thinking the way you do.

The digital world demanded that humans learn to think like machines — exact spelling, exact filenames, exact folder paths, exact keywords. And billions of people complied, awkwardly, because they had no choice. But it was never natural. There was always a translation tax — the cost of converting human memory into machine-retrievable form. It’s dehumanizing.

Consider how the food of different cultures resonates with the senses. French food is butter, basil, thyme, leeks, and wine…. Italian food is similar but omits the butter and adds tomatoes, eggplant, olive oil, and anchovies… Japanese food has an altogether different flavor profile with tamari. Mexican food adds corn, chiles, and lime…. Every culture has its unique set of flavor profiles, even when using similar ingredients.

Human memory doesn't work in precise terms. It works in associations, much like the flavor profiles of foods from different cultures. You don't remember the filename. You remember the feeling of the conversation, the person's voice, the problem you were trying to solve, and the season it happened in. That's not imprecision — that's how rich, layered, contextual memory actually works.

Fast food solved the precision problem by eliminating subtlety. Everything standardized, everything labeled, everything findable. You always know exactly what you're getting. And you always get exactly that — nothing more.

The ramen shop doesn't work that way. Their broth took 18 hours of slow cooking. The ingredients aren't on the menu. You can't reverse-engineer it from a label. But you know it when you taste it — and you remember it years later without being able to name a single ingredient precisely.

ONDA Replay uses tags to get you close to the audio file, like how we remember the meal from the place we ate and who was there.

You put in what the conversation tasted like to you — your words, your associations, your inexact human memory of what mattered. The system doesn't correct you. It finds the neighborhood. You recognize it when you see it.

That's not a workaround for imprecision. That's the design honoring how humans actually remember anything. And now with Replay, your memory includes the memories that matter.

We need to draw some boundaries here.

We’re considering how we can help you use free tools you already have to print this on your computer printer.

"We won't plan your wedding. But if you recorded the conversation where you and your partner decided what you actually wanted — Replay will help you turn that into a document your caterer, florist, and venue can all work from."


Contact us

Interested in working together? Fill out some info and we will be in touch shortly. We can’t wait to hear from you!