One day I was debugging code and architecting systems. The next I was trying to work out why two engineers sitting six feet apart in a Slack channel had developed the kind of mutual resentment that requires a mediator, a retrospective, and a conversation I had no idea how to have.
I first became a manager in 1981. The biggest challenge then was delegating work to somebody ten feet away.
The traditional playbook assumed you could read body language, catch people in a hallway, and build a culture through proximity and shared coffee. That playbook is now about as useful as a fax machine.
Everybody is working this out as they go. Some of us have simply been doing it longer and made more spectacular mistakes along the way.
So the book is not a set of principles handed down. It follows three managers across fourteen chapters, watching them fail in ways a reader will recognise before they adapt.
Why is the book built on StoryBrand?
Because most management books put the reader in the wrong role.
The standard structure is outside in. Here is a principle, here is the evidence for it, here is how to apply it. The reader is a student receiving instruction, and instruction is remarkably easy to nod along with and never use.
StoryBrand reverses that. It is Donald Miller’s framework, grounded in the mechanics of story. A hero faces a problem, meets a villain that makes it worse, finds a guide with a plan, takes action, and is changed by the result.
Applied here, the reader is the hero. The three managers in the book are guides who have already faced what the reader is about to face. The framework is the plan and the transformation is what becomes possible once it is executed.
That produces writing a reader experiences instead of observes, which is a different outcome from being informed.
The book on this: Street-Smart Management Wisdom follows three managers through fourteen real problems, built deliberately on the StoryBrand framework so the reader is the hero, not the student.
How is each chapter structured?
Around five beats, every time, and the repetition is deliberate.
The villain, meaning the specific force working against the character in that chapter. The stakes, meaning what fails if they do not solve it. The guide, the person who arrives carrying a framework. The plan, which is a specific named methodology instead of encouragement. And the transformation, the before and after that closes the chapter.
The action items at the end are the reader’s version of the plan.
The details of each situation are not the point. The shape of the problem and the shape of its resolution are, which is why the same five beats can carry fourteen different management problems without the book becoming repetitive to read.
Who are the three managers?
Three specific people, not three archetypes, and that distinction took work.
Maya Delacroix is twenty-six, first-generation Haitian-American, raised in Miami. Her father is an electrician and her mother does medical billing, and she got into engineering on a scholarship by being the person who solved the problems everybody else abandoned. Precise, self-contained.
David Rodriguez is thirty-four, third-generation Mexican-American from San Antonio. His grandfather ran a restaurant, his father sells insurance, his mother teaches middle school, and he learned early that warmth is a skill. He is the one who remembers your child’s name and buys tacos when the team ships something.
Keisha Williams is fifty-two, Black Southern, raised in Birmingham. Her grandmother marched. Her mother was a union steward for thirty years. Keisha grew up understanding institutions from the inside. Who holds power, where decisions really get made, and why some things last while others do not.
Why does the cast matter to a management book?
Because a book that speaks to one kind of manager speaks to a fraction of its audience.
That is the practical reason and it is not the only one. Three people with different backgrounds encounter the same management problems differently, and watching three different routes to the same hard-won understanding is more instructive than watching one.
Keisha reads a political problem the way somebody raised around union stewardship reads it. David reads a team chemistry problem through warmth as an acquired skill. Maya reads a hiring problem the way somebody who got in on merit and precision reads it.
Almost everybody who has ever been handed responsibility they did not feel ready for can find themselves in one of the three.
What does the book do about failures nobody teaches?
It gives them chapters instead of a paragraph of sympathy.
Keisha builds a knowledge vault and then takes a holiday that was supposed to be ten days. By day three her phone has forty-seven messages. By day four somebody on the floor has made a supplier decision she would never have made and cannot reverse. By day five she is on a beach answering an email about a process question that is in the documentation. Her documentation, which she wrote, and which her team cannot find without her, because nobody has ever been asked to look.
She flies home early and tells her husband it was urgent.
Documenting a process is not the same as building a team that uses documentation, and the chapter is the distance between those two things.
What happens when good work gets undone?
Chapter eleven, and it is the one most management books will not write.
Keisha did everything correctly on her way out. Documented the processes, cross-trained her successor, spent six months making sure he understood not only what she did but why. Thorough, deliberate, and confident she had built something that would last.
Six months after the promotion, former colleagues start sending carefully worded messages. The kind people write when they are not sure they are allowed to say what they want to say.
Reading between the lines, which she has done her whole career, the thing she built is coming apart.
A management book that only shows things being built teaches half a job. Watching a competent handover fail anyway is more useful than another chapter on delegation.
How does the book handle office politics?
By making the difficult boss competent, which is the harder version.
David had always believed in keeping his head down and doing good work. That belief served him for most of a career and then failed completely the moment Victoria Brennan became his boss. High expectations, low context, and a talent for making decisions in meetings he was not invited to and then holding him accountable for them.
She was not incompetent. That is the frustrating part, and it is why the chapter works. Her strategic thinking was sharp. She simply had no interest in his opinion.
Writing the villain of a politics chapter as a fool would make the reader feel better and teach them nothing. Most people who make your working life difficult are good at their jobs, which is exactly why the usual advice does not apply.
Is the book also a work sample?
Yes, and it says so in the front matter instead of leaving it implied.
If a ghostwriting client is looking at this book as an example of what I do, the structure is not accidental and it is not decorative. It is the architecture that makes management content readable. Informative is a lower bar and most books in the category stop there.
The framework applies to any business nonfiction. Memoir, thought leadership, how-to, case study. The result is the same. A reader who finishes having experienced a transformation and not attended a lecture.
There is an appendix documenting the StoryBrand architecture of the book itself, so a reader who wants to see the machinery can look at it directly.
What management problems does the book cover?
The fourteen that arrive.
A new manager’s reality check. Building a leadership operating system. Hiring. Communication. Performance management. Reading people and building trust. Building systems that survive you. Managing up and across, which is the politics chapter.
Then leading through change, scaling teams, and the one most books avoid, which is what happens when good work gets undone.
Then the transition from technical leader to people developer, crisis management under fire, and what mastery means, which is a longer trajectory than any single chapter can close.
The Guides That Get Your Book Written, Published, and Sold
Four short, practical guides on writing, publishing, and selling your book, plus the occasional note when there's something worth your time. No fluff, no daily inbox clutter. Drop your email and they're yours.
We use MailerLite to manage our list and send these emails. Your address is used only to send you what you signed up for. We will not sell it, share it, or use it for anything else, and you can unsubscribe anytime.