Project Manager

Own the execution. Make launches predictable. Remove the chaos. A Brave Books launch involves product development, marketing, fulfillment, creator management, Amazon optimization, and PR — all moving in parallel. Timelines are aggressive. Dependencies are complex. One bottleneck in production delays the entire marketing calendar, which delays the revenue. We have great launches. We also have launch chaos. We need someone who makes launches predictable . What you'll actually do: Build the launch playbook. We have a Launch Bible (our strategic foundation document). You'll take that and turn it into a concrete 12-16 week timeline with deliverables, owners, and decision gates. You'll own the fact that everything that was supposed to happen actually happened, on time. Daily coordination across departments. Product development is waiting on final author feedback. Marketing is waiting on final product specs. Fulfillment needs 4 weeks to ramp. You'll see these conflicts coming and surface them before they become crises. Teach teams to think in dependencies. "We said launch day was June 1st, but product isn't delivering the final file until May 20th." That's fine, as long as we knew that in February and planned around it. You'll make sure teams think forward, not backward. Troubleshoot the actual problems. When something goes wrong, you diagnose it. Is it a timeline problem? An information problem? A resource problem? A skill problem? You fix the machine, not the symptom. Scale the system. We manage 30+ launches in a year. That's unsustainable if each launch requires a custom operation. You'll identify repeatable steps, codify what works, and make each subsequent launch smoother than the last. Be the translator. Engineers talk to marketers. Fulfillment talks to product. You translate between languages and keep everyone aligned on what's actually happening. What we're looking for: Bias toward clarity. You'd rather write out the plan and have everyone disagree than leave it vague and discover surprises later. You believe unclear expectations are the root of most problems. Comfort with ambiguity and the ability to create structure from it. We don't have perfect playbooks yet. You'll build them as you go. Systems thinking. You see the whole launch as a system, not a list of tasks. You know that optimizing one step often breaks three others, so you optimize for flow. Grit. You'll hit problems that require you to debug something nobody fully understands. You won't give up. You'll keep asking better questions until the problem becomes solvable. Bonus: Publishing, software, or product management background. Or just "I've managed large, complex projects." Why you'd want this job: You become the keeper of operational rhythm. As we scale, your systems will enable dozens of people to work in parallel without stepping on each other. You'll see direct impact — better launches, fewer fires, happier teams. If you're a natural organizer who wants to prove you can scale operations at a growing company, this is your shot. #J-18808-Ljbffr