The PM Onboarding Copilot
How I Made Strategic Impact in Two Weeks
The Friday Afternoon Revelation
A product strategy discussion with the CEO after just two weeks.
It was Friday afternoon, and I found myself presenting a comprehensive product strategy to my CEO. What started as a routine two-week check-in had evolved into something much more significant. I set the expectation that we would use this time to discuss the strategic direction I'd been developing, which meant I needed to demonstrate a deep understanding of our business components, stakeholder dynamics, current market position, and future opportunities.
As we dove into the conversation, something remarkable happened. The discussion flowed as if we'd been collaborating on this strategy for months, not days. At a high level, we explored market positioning, competitive dynamics, and product vision with the kind of depth that typically takes quarters to develop. When he paused and said, "It feels like you've been working here for months," I felt a surge of surprise and validation.
That moment crystallized something important for me. This wasn't just about ramping up with speed; it was about achieving velocity. Speed is moving fast. Velocity is moving fast in the right direction with the right context and documentation to build upon. I had managed to absorb not just information, but the key insights needed to contribute meaningfully from day one.
This experience reveals a fundamental shift happening in product management. Rather than accepting the traditional 30-60-90 day ramp-up timeline, AI tools can enable us to compress months of learning into weeks of focused, directional progress. The PMs who can master this approach—who can jump in, make an impact, and make the right impact with true velocity will have a decisive competitive advantage in shaping both their careers and their companies' market positions.
The Evolution: From Static Plans to Strategic Velocity
Most companies provide their PMs a structured 30-60-90 day plan, and while these frameworks have served us well, they're ripe for evolution. At Farm'd, I built documentation from scratch with a 10-person team, a creative challenge that taught me to work effectively with minimal structure. Stord had comprehensive Confluence pages and clear milestones, representing the gold standard of traditional onboarding. Yet even with excellent documentation, I sometimes found myself overwhelmed by the sheer volume of information, struggling to identify what mattered most for immediate strategic impact. At Nerdy, I encountered the opposite extreme: sparse documentation, disconnected pieces, and that familiar feeling of trying to assemble a strategic puzzle without all the pieces.
That's when an interesting realization struck me. Here I was, working to onboard at a company building AI-powered education products, while still relying on static frameworks that hadn't adapted to the AI tools now available to us. It seemed like a missed opportunity. If we were innovating with AI for our users, why weren't we exploring how these same tools could enhance our own team development and onboarding processes?
This realization became the catalyst for everything that followed. The breakthrough came through Tal Raviv's PM copilot framework, which I discovered through both his Maven course and a transformative four-hour session with the Supra product community. Tal's approach revealed something crucial: AI tools don't just make us faster, they make us better decision-makers by serving as thought partners that challenge our assumptions and push our thinking.
As I prepared to join NewtonX, I realized this was my chance to test a radical hypothesis: what if I could compress traditional onboarding timelines not just through speed, but through strategic velocity? I immediately built my "PM Onboarding Copilot" using Claude Projects, feeding it the most relevant document and context I could gather. Then I discovered the power multiplier: combining this with Granola for contextual conversation capture and Wispr Flow for seamless dictation.
This wasn't just about consuming information faster, it was about transforming how I could synthesize strategy, develop marketing collateral, structure team priorities, and engage in deep strategic thinking from day one. The traditional approach treats your brain like a storage device. The AI-enhanced approach treats it like a strategy engine.
The Workflow: Three Tools, Infinite Possibilities
The magic isn't in a single tool, but instead it's in how three AI-powered workflows amplify each other to supercharge the onboarding copilot. While Claude Projects, Granola, and Wispr Flow are interchangeable based on immediate needs, the real unlock happens when all three feed into the Copilot ecosystem. Granola captures and synthesizes stakeholder conversations, Wispr eliminates type-to-input friction for rapid reflection and questioning, and Claude Projects transforms this continuous stream of context into clear direction and outcomes. Each tool enhances the others, creating a compounding effect that traditional sequential processes can't achieve.
Building the PM Onboarding Copilot began by drawing inspiration from Tal Raviv's PM Copilot framework. I created a Claude Project titled "PM Onboarding Copilot". The general description is "Product Manager Onboarding Copilot for NewtonX -- an expert guide, mentor, and resource during your onboarding journey as the Product Lead for Hub." The project instructions cover core responsibilities, interaction approaches, key capabilities, organizational navigation, and behavioral guidelines—essentially creating a strategic thinking partner that understood both PM fundamentals and my specific context.
The full project instructions are available for subscribers—reach out if you are interested.
Granola became my conversation intelligence engine. Perfect timing, their folder feature launched right as I started at NewtonX. I organize stakeholders into team-based folders—Product, Data, Sales, Marketing, Executives, etc, and capture every onboarding conversation either through recordings (with permission) or detailed notes via Wispr dictation.
Then came the key unlock: Granola's chat feature within each folder. I used a specific prompt:
"Provide a very detailed output of the key points noted from the various team members. I will use the outputs for my Onboarding Copilot. Think about areas like: What are the key pain points? What are the opportunities for growth? Who are our customer personas? Where do the team members see our company and product in the market today, and where can it go?"
Wispr eliminated the friction between thought and capture entirely. Instead of losing momentum while typing out complex strategic reflections or conversation insights, I could speak my analysis directly into the workflow at the speed of thought. It was about preserving the cognitive flow state that's essential for connecting disparate insights across stakeholder conversations. The moment you break rhythm to hunt and peck on a keyboard, you lose the neural pathways that link the dots. Wispr keeps those connections alive.
The feedback loop became addictive. After ingesting the relevant documentation & stakeholder conversation summaries into Claude, I'd immediately ask: "Where should I focus first? What gaps do you see? Help me connect the dots." The copilot would synthesize patterns across documents and teams, highlight contradictions, and suggest points I hadn't considered. This created a continuous "What's next?" momentum that built exponentially throughout that first intensive week.
The human touch remains critical. While AI accelerates processing, I still relied on guidance from my manager, CEO, and product team to prioritize which documents truly mattered versus those that were merely nice-to-have background reading. The optimal approach isn't about feeding everything into the Copilot; rather, it is about curating the essential context that drives better & faster decisions.
The Reality Check: Challenges and Solutions
This approach isn't foolproof—it requires intentionality and the right conditions to unlock its full potential. After implementing this across my own onboarding and sharing it with our new GM, I've identified the key obstacles you'll face and practical ways to navigate them.
Challenge 1: Poor or Missing Documentation. The biggest limitation hits when companies lack structured knowledge bases. If documentation is sparse, outdated, or scattered across systems, your AI copilot has nothing meaningful to synthesize. The solution? Lean heavily into dictation and amplified conversations. Use Wispr (or any preferred dictation tool) to rapidly capture what you're observing, create structured outlines of missing information, and schedule more stakeholder interviews than usual. Think of yourself as simultaneously onboarding and creating the documentation foundation that future hires will benefit from.
Challenge 2: The Customer Feedback Gap. Internal stakeholders will share their perspectives, but validation through actual customer metrics and qualitative feedback is often harder to access, which is critical for informed strategic decision-making. I discovered this limitation early; my copilot could synthesize internal opinions but lacked the context of the customers' voices. The bridge solution is treating your onboarding copilot as Phase 1, then transitioning it into a full PM copilot that incorporates customer research, usage data, and feedback loops as you gain access to these systems.
Challenge 3: Stakeholder Comfort with AI and Recording. Not everyone is comfortable being recorded or knowing their feedback will be processed by AI tools. Always start conversations with: "Are you okay with recording this, or would you prefer I take notes?" Respect their preference completely. If they decline recording, capture notes traditionally, then use dictation afterward to process them into your system. The goal is to gather insight, not force a specific method.
When This Approach Won't Work. This methodology requires baseline organizational openness to accelerated timelines and some form of existing documentation or institutional knowledge. If you're joining a highly secretive organization, a company in crisis mode, or a role that requires extensive regulatory training, traditional approaches may still be necessary.
Success Prerequisites. This approach scales when you have: willing stakeholders, some baseline documentation (even if imperfect), and organizational openness to accelerated timelines. The beauty is scalability. I shared my Claude project template directly with our new GM, giving him instant access to all context and relationships. Rather than recreating 30-60-90 day plans, you can share structured AI copilots that enable two-week contribution timelines.
The key insight: this works best when you're building the bridge between traditional onboarding and AI-enhanced acceleration, not trying to replace human connection entirely.
The Future: Beyond Traditional Onboarding
We're living through a fundamental shift that mirrors the early dot-com era, a moment when new technologies unlock entirely new possibilities. Just as the internet revolutionized how we work, communicate, and innovate, AI is creating unprecedented opportunities across every aspect of business. Onboarding represents one of the most immediate and impactful areas ripe for transformation. Just as static websites gave way to dynamic, personalized experiences, traditional 30-60-90 day templates can be entirely replaced by AI-powered systems that compress months of learning into weeks of strategic contribution. My CEO's reaction after two weeks—"It feels like you've been here for months" —isn't an anomaly. It's a preview of the new standard.
The competitive advantage for individual PMs is becoming undeniable. Companies can now gauge ROI immediately rather than waiting months to see the impact. Early adopters who master AI-first workflows—building copilots, automating competitive analysis, synthesizing user research in real-time—aren't just moving faster, they're developing pattern recognition that identifies the right opportunities with unprecedented velocity. During hiring processes, the question will shift from "Can this PM eventually contribute?" to "How quickly can they drive meaningful outcomes?"
Organizationally, we're approaching an inflection point. Static Google Docs and Confluence templates will evolve into dynamic, personalized onboarding agents. Imagine joining a company where an AI agent has already synthesized every relevant document, generated a custom hour-long podcast tailored to your specific role and context, and created visual maps of stakeholder relationships and business dynamics. Companies like Rippling for HR automation and Glean for enterprise search are building the infrastructure, now someone needs to connect the dots for onboarding transformation.
The technology roadmap is accelerating toward agentic workflows that integrate seamlessly with existing company systems. Rather than manual document curation, future onboarding will feature AI agents that automatically extract key information, identify knowledge gaps, and create personalized learning paths.
This is just the beginning of what's possible when we apply AI thoughtfully to product management fundamentals. As more PMs experiment with AI-enhanced onboarding, we'll discover new patterns, tools, and methodologies that push the boundaries even further. The early movers will define the next decade of product management. If this resonates, you're already ahead of the curve. Start building your onboarding copilot today, share your experiments, and help establish the new standard for what professional velocity looks like in an AI-first world. The future of onboarding is here!
Ready to get started? Reach out if you would like the complete Claude Project template, the Granola workflow setup, or if you'd like to share your own onboarding innovations.
Amazing content! I'd love to see the Claude Project Instructions you used :)
great article! could you pls share the Claude Project Instructions?