Read JTOS Part 1: The Cognitive Engine, JTOS Part 2: Foundry Logs, JTOS Part 3: Story Assets, JTOS Part 4: The Synthesis Engine
What You Will Learn: Why sharing facts and frameworks is rarely enough to inspire change, and how to use “Story Assets” to provide the human proof your ideas need to stick. How You Can Apply It: You will learn a structured method to capture your raw, lived experiences—including sensory details and emotional baselines—so you can retrieve them later to build trust and connection when you communicate.
We love data. We build spreadsheets, draw charts, and establish logical frameworks. But data rarely changes behavior. No one alters the trajectory of their life or their business because you showed them a pie chart. They change because you told them a story they could see themselves in.
Last week, we discussed the first half of the Jason Todd Operating System (JTOS): the Foundry Log. A Foundry Log extracts the unarguable truth from a concept. It is the philosophical and tactical framework. But a framework alone is sterile. It needs proof.
If you want to move people—whether you are advising a founder in a boardroom, writing a book, or speaking on a stage—you have to connect your abstract frameworks to raw human friction. You do this by capturing and storing Story Assets.
What is a Story Asset?
A Story Asset is the historical, narrative proof of a Foundry Log. If the Foundry Log is the skeleton of an idea, the Story Asset is the muscle and skin.
It is a captured memory of a lived experience. It is the time I crashed my car, the time I sold a business, or the time a relationship thrived against the odds. We experience these profound moments constantly, but we trust our brains to remember them. That is a mistake.
Over time, human memory fades. We remember the conclusion of the event, but we forget the texture of the moment. When the texture is gone, the story loses its ability to connect with an audience. To prevent this, I do not rely on my memory. I capture the event as a Story Asset while it is still fresh.
The Architecture: Capturing the Human Element
When I build a Story Asset in my system, I do not just write a quick summary of what happened. I run the memory through a specific architecture to ensure I capture the human element. I focus on two specific layers:
1. The Sensory Data When we recall a story years later, we often strip away the environment. I force myself to write down the physical details. What did the room smell like? What did the chair feel like? What was the temperature? I write down the specific, unedited words that were spoken. Capturing this sensory data allows me to put the reader or the audience inside the room with me when I retrieve the story later.
2. The SASHET Baseline Business leaders often use sterile metaphors to describe how they feel. They talk about “bandwidth,” “capacity,” or “friction.” When I build a Story Asset, I do not use those terms. I map the raw human emotion using the SASHET baseline: Sad, Angry, Scared, Happy, Excited, Tender.
I force myself to identify the actual, foundational feeling of the moment. Was I angry, or was I actually scared? Documenting this baseline ensures the story retains its authentic emotional resonance.
The Use Case: Grounding Theory in Reality
The power of capturing Story Assets becomes obvious when it is time to create.
When I sit down to write a chapter of a book or prepare a keynote presentation about the “fear of failure,” I do not just give my audience a dictionary definition of fear. I query my system. I pull up the Foundry Logs on the mechanics of fear, and then I pull up a Story Asset about my seventh-grade spelling bee.
I retrieve the sensory data of standing on the stage. I retrieve the SASHET baseline of feeling scared and wanting to fit in. I pair the unarguable truth of the framework with the visceral reality of the childhood memory.
This process makes the abstract truth real. It allows me to communicate fluidly and connect with people on a human level, rather than just lecturing them from a whiteboard. I am never pulling ideas out of thin air; I have a database of lived proof waiting to be used.
Next week, we will conclude this series by looking at the Synthesis Engine. I will show you how to tie your Foundry Logs and Story Assets together using tags, and how you can set up a simple version of this system for yourself.
Read JTOS Part 4: The Synthesis Engine
The Bridge: If you are communicating your vision but your team is not engaging, you do not need to speak louder. You need a better connection point. Explore the Story Assets on Communication to see how narrative drives action, or reach out for Advisory Support to refine your leadership messaging.