Skip to content

personal-context.example.md

Latest commit

 

History

History
67 lines (50 loc) · 4 KB

personal-context.example.md

File metadata and controls

67 lines (50 loc) · 4 KB

Personal Context

This file is about YOU, not your company. Fill it in so every skill adapts to your seniority, communication style, and organizational reality. Company/product context lives in domain-context.md. This file is personal.

Privacy note: This file may contain career information. Add it to .gitignore if you don't want it committed to a shared repository.

Your Role

  • Title: [e.g., Senior Product Manager, Head of Product, VP Product & PMM]
  • Seniority level: [Junior PM / Mid-level PM / Senior PM / Lead/Staff PM / Head of Product / VP/CPO]
  • Years in product: [e.g., 3 years]
  • Team you lead: [e.g., "I lead a squad of 1 PM + 4 engineers" or "I manage 6 PMs" or "Individual contributor"]
  • Scope: [e.g., "I own the invoicing module" or "I own the entire product" or "I own growth and activation"]

Your Background

  • Previous roles: [e.g., "Was a software engineer for 5 years before moving to product" or "Came from consulting" or "Career PM"]
  • Domain expertise: [e.g., "Deep in fintech, new to ERP" or "10 years in B2B SaaS" or "First time in a regulated industry"]
  • Strengths: [e.g., "Strong on data analysis, weaker on stakeholder communication" or "Good at strategy, learning execution"]
  • Growth areas: [What you're actively working to improve — e.g., "Learning to write better PRDs" or "Getting better at saying no"]

Your Organization

  • Who you report to: [e.g., "CTO" or "VP Product" or "CEO directly"]
  • Key stakeholders: [e.g., "CEO (hands-on, wants weekly updates), Engineering Lead (collaborative), Sales Director (pushes for features)"]
  • Decision-making style: [e.g., "Consensus-driven — I need buy-in before moving" or "I have full autonomy on my module" or "Everything goes through the CEO"]
  • Team culture: [e.g., "Data-driven, async-first" or "Fast-moving startup, decisions made in hallways" or "Enterprise — formal processes, quarterly planning cycles"]

Communication Preferences

  • How you like to receive feedback: [e.g., "Direct and blunt" or "Constructive with suggestions" or "Show me examples, not just critique"]
  • Output format preference: [e.g., "I want concise outputs I can edit" or "Give me comprehensive first drafts" or "Bullet points over paragraphs"]
  • Language: [e.g., "English" or "German for internal docs, English for product specs" or "Mix of English and German"]
  • Formality level: [e.g., "Casual (Du-Form)" or "Professional (Sie-Form for external)" or "Depends on audience"]

Current Focus

  • This quarter's priorities: [e.g., "Ship the new reporting module, reduce churn in SMB segment, define pricing for AI features"]
  • Biggest challenge right now: [e.g., "Stakeholder alignment — CEO wants feature X, data says feature Y" or "We're post-PMF but pre-scale, figuring out what to do next"]
  • What you need most from this toolkit: [e.g., "Help me write better specs" or "I need to build the GTM motion from scratch" or "Coaching on PM frameworks I haven't used before"]

Skill Level Self-Assessment

Rate yourself so the toolkit adapts its guidance depth. 1 = "Teach me" to 5 = "I'm an expert, just give me the template."

Area Level (1-5) Notes
Discovery & Research (JTBD, interviews, personas) [1-5] [optional context]
Strategy (OKRs, roadmaps, quarterly planning) [1-5]
Specs & Requirements (PRDs, user stories) [1-5]
Pricing & Monetization [1-5]
Data & Metrics (funnels, A/B tests, dashboards) [1-5]
Communication (exec updates, decision docs) [1-5]
Go-to-Market (positioning, battlecards, launches) [1-5]
Operations (retros, post-mortems, processes) [1-5]

What To Avoid

  • [e.g., "Don't over-explain basic PM concepts — I know JTBD and OKRs well"]
  • [e.g., "Don't generate 10-page documents when I ask for a quick draft"]
  • [e.g., "Don't assume I have data — we're early stage and flying blind on metrics"]
  • [e.g., "Don't use the word 'stakeholder' — our CEO hates it"]