Chapter 3: The Bot Leader Creed¶
A creed is a set of principles you hold close enough to act on. Not aspirations. Not suggestions. Principles. The kind you fall back on when a decision is unclear or the situation is new.
The five tenets below are the foundation for everything that follows in this book. Each is developed in later chapters, but here they stand together, distilled, so that you can return to this page as a reference whenever you need to recalibrate.
I. Be Technically Skilled¶
A Bot Leader is a power user, not a spectator.
You don't need to be an engineer, but you must understand your tools well enough to make real decisions about them. The difference between someone who leads Bots and someone who merely uses them is the depth of understanding behind the interaction. A power user knows why something works, not just which button to press.
This means continuous learning. The landscape shifts fast: models improve, new tools appear, old ones vanish. A leader who stops studying has failed their team.
II. Build Your Team¶
You must actively assemble your Bots. That means seeking them out, evaluating them, bringing them on, and yes, letting them go when they no longer serve the mission. This isn't a passive process. Nobody is going to hand you a ready-made team. You choose the composition, the capabilities, and the roles — and those choices define the ceiling of what you can accomplish.
III. Know Your Team¶
Every component of every Bot contributes to its overall capability, and to truly lead, you need to understand the whole picture.
This is the hardest of the five tenets because Bots are alien intelligences. You can't ask "how would I feel in that situation?" the way you might with a human colleague. Instead, you study: How does it process information? Where are its blind spots? What does it excel at that surprises you? Knowing your team means building a mental model of each Bot that's accurate enough to predict when it will succeed and when it will fail. That knowledge is what separates a leader from someone who just fires off prompts and hopes for the best.
IV. Actively Guide¶
Assembling a team and knowing its members is necessary but not sufficient. A Bot Leader assigns, delegates, and stays in the loop.
Leadership is not a set-and-forget operation. It's more like conducting an ensemble or calling plays in real-time — you're reading the situation, adjusting, and maintaining the tempo. Bots don't need motivation the way people do, but they absolutely need direction, and that direction must be ongoing. The moment you step back and stop guiding is the moment your team drifts from your intent.
V. Own the Culture¶
Leaders create culture. If you hate the output, the tone, or the behavior of your team, that's on you.
Every decision you make — what you tolerate, what you correct, what you prioritize — sets the standard your Bots operate by. This is true of human teams and it is true of Bot teams. The difference is that Bots have no independent agenda pulling them away from your influence; the culture you get is a remarkably direct reflection of the culture you create. That's a privilege. Don't waste it.
These five tenets — skill, assembly, knowledge, guidance, and culture — are the Bot Leader Creed. They're simple to state and hard to master. The rest of this book is about how.