Notes on training out loud.
What we learn building Frank, with the detail that does not fit in a demo: how deliberate practice works, how a voice is read against its own baseline, and how a program that actually works gets built.
Working notes, signed by whoever lived them.
Every note comes out of something we solved building Frank: a design decision, a finding from measuring voice, a program that got built differently. Published with a date and the name of whoever wrote it.
Deliberate practice
Why repeating a hard conversation with real friction is different from taking a workshop, and how that repetition is designed so people improve at what costs them, not at what they already do well.
Measuring voice
What can be read from a voice compared against its own baseline, what cannot, and why the report is delivered when the session ends and never during it.
How programs get built
The path from the documents a company already has to a set of stories approved by a person: what Frank proposes, what gets corrected by hand, and what gets rejected.
To get every new note as it lands, there are two paths. Write to the team, which answers in person. Or follow Frank on LinkedIn, which is where we announce first.
Worth reading right now.
Three resources on the site that answer concrete questions about the product.
Tutorials
Step-by-step guides: preparing your company context, approving the scenarios Frank proposes, and reading a session report.
Glossary
The terms we use, explained without jargon: baseline, delta, key moment, nature of the scenario.
Community
Who the Frank community is for, what gets shared there, and the two channels where the team reads and answers in person.