# How should Product Managers and non-technical professionals approach Claude Code specifically?

Source: https://www.kingscrosslabs.com/guides/claude-code/product-managers-claude-code
Author: Mika Reyes, Nick Reyes (King's Cross Labs)
Published: 2026-05-07
Updated: 2026-11-16
Topic: Role-specific advice

## Short answer

Product managers should invest heavily in CLAUDE.md, describing their role, stakeholders, acronyms, and preferred output. Then turn recurring documents like PRDs, weekly updates, and interview summaries into skills, connect Notion, Calendar, Linear, and Slack through MCPs, and keep a living projects.md file linked from CLAUDE.md.

## The longer answer

1. Over-invest in `CLAUDE.md`: role, surface areas, stakeholders, acronyms, output shapes you care about.
2. Encode repeating docs as skills—PRD skeletons, weekly updates, interview summaries, competitive tear-downs.
3. MCPs for Notion, Calendar, Linear, Slack so work stays where your team already is.
4. Maintain a living `projects.md`; refresh after big meetings and link it from `CLAUDE.md`.
5. Desktop first; terminal later.

> Maven workshop: The cohort format is built for PMs and operators who want accountability while assembling their first real agent setup — [join here](https://maven.com/mika-reyes/master-claude-code-as-a-non-technical-pro).

---
Cite this page as: https://www.kingscrosslabs.com/guides/claude-code/product-managers-claude-code