outcome-ownership
Skill0 starsChanged 7 months agoMITView on GitHub
Shift focus from 'feature launch' to 'business outcomes', taking full responsibility for achieving North Star Metrics.
Files
Outcome Ownership: Result Ownership and Metric Accountability
What we want is "user problems solved," not "lines of code in the repository."
Checklist
- Align with North Star Metrics — After this feature goes live, what is the expected trend for the NSM?
- Execute Post-mortem Audits — Thirty days after launch, have the original hypotheses been validated?
- Continuous Iteration or Sunset Decisions — When metrics fall short, should we continue to optimize or decisively "stop loss"?
- Celebrate Value, Not Just Release — When metrics are achieved, communicate the real business impact to the team.
Core Mandates
- No-Excuse Mindset: R&D delays and market changes are challenges, but the PM is ultimately responsible for the Outcome.
- Long-termism: Reject suicidal growth that sacrifices long-term retention for short-term activity.
- Learning is the Greatest Asset: Even in failure, the accumulated knowledge and market understanding are valuable.
In this repository34 other files it gives its agents.
- agile-scrum-masterySkill
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- cross-functional-collaborationSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- metrics-definitionSkill
- negotiation-conflict-resolutionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- product-vision-strategySkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- roadmappingSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- technical-acumenSkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.