The Stories Behind the Stories: Daniel

SHOW NOTES

The Stories Behind the Stories Episode Daniel

Sometimes the limitation is the solution.

Daniel's structural engineer understood that. 

So did his clients. 

Once he finally told them.

Daniel's story is about a specific kind of professional distance. The kind that looks like success. Five years of impressive work. Respected clients. Projects delivered. And relationships that never quite deepened. That distance has a cost. Not always visible. But real. In this episode of The Stories Behind the Stories, I go deeper into the failure, success and passion stories behind the character — and into the real pattern I was observing when I wrote him.

RESOURCES 

How to Build Genuine Trust Through Storytelling.

The Programme Behind the Story:The Art of WorkLife Storytelling: Creating Three Fundamental Stories That Define Your Identity

Your Three Stories Takeaway

Before you go — something to take with you.

Your Failure Story.

What process have you kept invisible that would build trust if it were shared?

Your Success Story. 

When did a constraint lead you somewhere better than your original plan?

Your Passion Story. 

What do you see in a challenge that others don't yet see?

A Note to Listeners

Every Thursday a new episode of The Stories Behind the Stories continues.

From May 2026 — each new episode will be free for one week.

After that it goes behind the subscriber paywall.

One week to listen.

One week to experience the learning.

One week to build it into your working life.

If an episode resonates — pass it to someone who would find it useful.

A colleague.

A client.

A friend.

That’s how this work finds the people it’s meant for.

After one week each episode joins the back catalogue — available to subscribers only.

Transcript

SPEAKER_00 0:08

Sometimes the limitation is the solution. Daniel's structural engineer understood that. So did his clients, once he finally told them. Hello, it's Carmel from School of Work Life. Welcome to Stories Behind the Stories, where I go deeper into the work life stories I've crafted, the thinking behind the ideas, the experiences that shape that thinking, the lessons learned from those experiences. Today's episode is Daniel. His story is featured in the episode How to Build Genuine Trust Through Storytelling. In the last episode I went deeper into Sarah's three stories. Today I want to go deeper into Daniel's failure, success, and passion stories. Together they reveal something that no single story could show alone, who he is professionally, what shaped him and what drives him, the story behind his stories, what almost went wrong. Credibility is built through competence. Trust is built through openness. Daniel had perfected the art of the flawless presentation. For five years, every rendering polished, every timeline precise, every narrative seamless, and every relationship formal, impressive, professional, distant. Daniel's story is about a specific kind of professional distance, the kind that looks like success. Five years of impressive work, respected clients, projects delivered, and relationships that never quite deepened. That distance has a cost, not always visible, but real. Daniel's failure isn't a single mistake. It's five years of presenting the finished work without ever sharing the journey that created it. Clients saw the outcome, they never saw the thinking. Here's what I think was behind that. Daniel had been trained to present solutions, not struggles. Polished was professional, process was personal, and personal felt risky. So he kept the real story hidden behind a rendering, behind a timeline, behind a seamless narrative. Daniel's clients respected what he delivered, but they never truly understood how he worked. Those are two different things. Respect for outcomes is transactional. Trust is thinking is something deeper. It's what creates partnerships that loss beyond the project. And that deeper trust requires something. When only the finished work is shown, clients can evaluate the outcome, but they can't evaluate the thinking. And thinking is what they're really trusting. Every time they hire someone, his success story begins with a question he hadn't prepared for. The CEO doesn't ask about the design. She asks what almost went wrong. And Daniel does something he's never done before in a client meeting. He closes his laptop, walks to the drawing board, and tells the real story, the constraints, the complications, the moment his structural engineer said something that changed everything. What if the constraints are the design? The room shifted, not because the design changed, because they finally understood the architect behind it. What strikes me about that question, what almost went wrong, it's an invitation to stop presenting and start sharing. The CEO wasn't evaluating the design. She was trying to understand the architect, how he thinks, how he works, how he handles the difficulty. That's what she needed to trust him, not the rendering, the thinking behind it. Daniel's passion story goes deeper than design. He isn't driven by creating beautiful buildings. He's driven by what constraints reveal, the limitation that becomes the opportunity, the problem that becomes the solution, the awkward angle that becomes the dramatic space. That's when architecture feels meaningful to him, not when everything goes to plan, when something unexpected opens up something better. Constraints have always interested me, not as problems to solve around, as possibilities to move toward. Daniel's passion is that instinct made visible, the limitation that opens something up. That's not just an architectural principle. It's how the best work happens in any field. I recognize this instinct, the constraint that becomes the opening, the limitation that forces a better solution. School of work life was built inside constraints, limited resources, a global pandemic, a market that had lost its learning budgets, and those constraints shaped everything. The accessibility, the portability, the belief that learning should reach everyone, not despite the limitations, because of them. But that's not where the story ends. Morrison Industries approved the project, expanded it, and referred Daniel's firm to two other companies. Something that had never happened from a single client relationship, because the CEO didn't just tell them about the design, she told them about the architect. He showed us how the building actually came together. What I hope you take from Daniel, beyond the framework, beyond the architectural context, is something simpler. Trust doesn't grow from seeing the finished work, it grows from understanding how the work happens. Daniel is every professional who has hidden the real story behind a polished one, not because they had something to hide, because they thought polish was what professionalism required until they discovered that openness was what trust actually needed. From my notebook, a fact, I see myself in Daniel. The constraint that becomes the different solution. When markets crash and they do, two things happen. People lose their jobs and learning budgets disappear for those who remain. The people who find themselves out of work have to find their own development. The people who stay find their organization can no longer invest in theirs. And the people who go on to be self-employed, setting themselves up as freelancers, consultants or contractors, have to finance their own continuous learning from the start. That constraint shaped everything I built, not despite it, because of it. For individuals managing their own learning, for companies investing in their people's development, and for me as a creator, maintaining sustainable practice. Working with people who value the work. That's what makes it possible to keep creating it. Just that Daniel's client valued his work because the story behind the work brought them inside it. The limitations of who could access learning guided me toward different ways of delivering it. Story lessons, guided programs, question banks, a podcast, a newsletter, each one a different Dorian for different people at different moments. Daniel let the site limitations guide him toward a different building. The limitations of who could access learning guided me towards different ways of delivering it. On Daniel, I wrote Daniel because I wanted to write across industries to reach more people, to show that these stories work everywhere, in an architect's office, in a room where someone is trusting you with a 15 million building. To write Daniel, I had to learn about architecture, what renderings are, what structural engineers do, what constraints mean in that world, quick research, just enough to write with confidence, just to know enough to know what would be expected in that room. But something unexpected happened. The research opened up the story. I didn't know going in what Daniel's breakthrough would be. I didn't know about a structural engineer or the line that changed everything. What if the constraints are the design? That arrived through following the story that was unfolding on the page, through learning just enough about a world I didn't inhabit to find a story inside it. That's what research does in my writing. It doesn't just inform, it opens things up, takes me somewhere I didn't plan to go, which is exactly what happened for Daniel and for me. On the question, the CEO asked Daniel one question, what almost went wrong? Not what went right, not show me the impressive parts, what almost went wrong. That question is the most powerful in Daniel's story because it gave him permission to tell the truth, and in doing so created more trust than five years of perfect presentations ever had. What almost went wrong is a rare question. It comes from a place of genuine curiosity. That's what makes it powerful. It signals something important to the person being asked. I'm not here for the performance, I'm here for the truth. That's the kind of question I try to build into my work. Not because questions that invite the expected answer, questions that open up what's actually there. Your three stories before you go, something to take with you. Your failure story, what process have you kept invisible that would build trust if it were shared? Your success story, when did a constraint lead you somewhere better than your original plan? Your passion story. What do you see in a challenge that others don't yet see? In the next episode, I'll go deeper into Rachel's failure, success, and passion stories from the episode How to Create Strategic Influence Through Purpose Driven Storytelling to take you inside the story behind a story. Thank you for listening.