Books / Learning comic
The First 90 Days as a Manager
Theme: Professional Development
Maya was the engineer everyone asked for help. On her first day as a manager, she tries to keep being that person and accidentally becomes the person everyone waits for. Across ninety days, a small clinic software pilot gives her plenty of chances to learn: a silent colleague, an overconfident promise, a delegation she nearly takes back, and an incident that needs coordination rather than a hero. This original illustrated workplace story follows Maya and her team through practical conversations about ownership, trust, feedback, delivery and sustainable work. Warm humor and continuous consequences make the ideas approachable without pretending management has a perfect script. Eight chapters include page-linked companion notes and questions for reflection, discussion and trying a better next step.
Start reading →View in the interactive libraryAbout this book
Maya knows how to solve an engineering problem. People management is less obliging. On her first day in the new role, she receives a quieter chair, a congratulatory cupcake and the mistaken impression that she can keep doing her old job while adding everyone else's concerns. By the second day, her helpful rescue of a colleague's work has become a queue. The team is busy waiting for its fastest engineer. The First 90 Days as a Manager follows what happens next through one workplace story. Maya's team is building an appointment reminder pilot for a fictional clinic. The project gives the characters something to care about, disagree over, promise confidently and repair. The teaching arrives through their choices and consequences rather than speeches from an infallible leadership expert. Lin, an early-career engineer, wants support without losing the keyboard. Theo, a senior engineer and former peer, wants room to lead technical work without becoming everyone's emergency answer machine. Omar needs testing and support work to count as real capacity. Priya must turn a changing delivery plan into an honest customer conversation. Elena, Maya's manager, asks questions that expose the difference between personal output and a team that can act. Across eight chapters, Maya learns to listen before prescribing a fix, make one-to-ones useful, protect privacy without promising impossible secrecy, and keep small commitments. Delegation becomes a conversation about outcomes, authority, resources and checkpoints. A missed assumption forces an explicit scope decision. Feedback becomes specific enough to act on, and Maya discovers that receiving it requires resisting the urge to explain herself. When a duplicate reminder interrupts the pilot, the story slows down to show coordination, containment, honest updates, verification and learning. Nobody earns a cape for staying awake longest. The aftermath leads to harder questions about priorities, support coverage, working boundaries and whether the team can make a sound decision while Maya is away. Day ninety is a review point, not graduation from uncertainty. The artwork uses a consistent cast, expressive reactions, detailed office and city settings, and separately lettered speech. Every chapter contains twelve story pages. Matching companion notes follow the physical PDF pages, distinguish the visible dialogue from additional explanation, and provide retrieval questions with page-specific practical explanations. The editable manuscript and source preserve the story for future revision. This book is intended for new people managers, aspiring technical leads and readers supporting someone through that transition. It can be read for its workplace comedy, used in a discussion group, or revisited one decision at a time. Primary guidance from established management and engineering organizations informs the general concepts, but the characters, project and outcomes are fictional. No source endorses the story, and no fixed timetable or method guarantees the same result in another workplace. The clinic setting is illustrative, not clinical advice or a production implementation guide. The aim is modest and practical: notice the moment when another rescue is about to become a bottleneck, then choose a clearer, more supported way for the team to move forward.