product-methodology

You can trace product decisions by organizing strategy into an artifact pyramid with explicit SOURCES navigation, connecting L1 summaries and L3 dossiers directly to discovery references for auditable governance.

Structure opportunity solution trees and RICE prioritization within a references-driven workflow that organizes analyses into L1, L2, and L3 layers, ensuring scoring templates and discovery outputs remain traceable.

Establish a living spec-template workflow by creating a pyramid root and populating at least one L1 summary, an L2 analysis, and an L3 dossier sourced from references to align stakeholder communication.

Yes, artifact pyramids support product governance and MoSCoW prioritization by mapping L1, L2, and L3 outputs with traceable sources, ensuring decision logs and stakeholder communication remain auditable.

No dependencies are required to manage decision logs, as the framework relies entirely on a references-based loading system to connect discovery interviews, analyses, and scoring templates across the pyramid.

You need an artifact pyramid when your team struggles to justify and trace product decisions across discovery, prioritization, and delivery, requiring an auditable framework with explicit sources.