> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dacard.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Run a full diagnostic across frameworks

> Combine all three frameworks for the cross-framework read.

<Note>
  Three frameworks together give you a defensible read no single framework can produce alone. Score with Team Operations, run the Lifecycle assessment, run the Product Assessment, then read the tension map.
</Note>

# Run a full diagnostic across frameworks

As a leader, you want a complete diagnostic across all three frameworks so you can surface the deepest systemic issues in your org and build a defensible improvement plan.

## The three-framework diagnostic

Each framework answers a different question. Running all three together produces the cross-framework read.

| Framework                 | Question                            | Assessment type                            |
| ------------------------- | ----------------------------------- | ------------------------------------------ |
| **Team Operations**       | How capable is the team?            | URL score (automated, 27 dimensions)       |
| **Development Lifecycle** | Where are you in the build process? | Self-assessment (36 tasks across 6 stages) |
| **Product Assessment**    | How capable is the product itself?  | URL score (automated, 27 dimensions)       |

## Run the full diagnostic

<Steps>
  <Step title="Score with Team Operations">
    Head to `/score` and score your product URL. This produces the 27-dimension maturity read.
  </Step>

  <Step title="Run the Lifecycle assessment">
    Open the scored product and pick the **Lifecycle** tab. Work through all 36 tasks with your team.
  </Step>

  <Step title="Run the Product Assessment">
    From the scored product page, pick the **Product** view. This reads the product itself across 27 capability dimensions.
  </Step>

  <Step title="Layer the POM overlay">
    Open the **POM** tab to map your scores to Product Operating Model principles. This adds a proven methodology lens to your raw scores.
  </Step>

  <Step title="Read the tension map">
    Compare the three framework scores side by side. The gaps between frameworks surface your deepest organizational tensions.
  </Step>
</Steps>

## Reading the tension map

The most valuable read comes from comparing across frameworks.

| Pattern                        | Team   | Lifecycle | Product        | Read                                                  | Move                                          |
| ------------------------------ | ------ | --------- | -------------- | ----------------------------------------------------- | --------------------------------------------- |
| Strong team, weak process      | High   | Low       | Varies         | Talented team shipping unevenly                       | Invest in process maturity (Lifecycle stages) |
| Process-driven, low capability | Low    | High      | Low            | Playbook without execution                            | Hire or upskill before adding more process    |
| Capable product, weak ops      | Low    | Varies    | High           | Impressive product, unsustainable operations          | Build operational discipline before scaling   |
| Product ahead of team          | Varies | Varies    | Product > Team | Product has more capability than the team can sustain | Close the ops gap or reduce surface area      |
| **Aligned and compounding**    | High   | High      | High           | Team, process, and product reinforcing each other     | Maintain the flywheel, extend the lead        |

## The POM overlay

The Product Operating Model overlay maps 20 principles to your Dacard.ai scores. It bridges aspiration and measurement.

* **Before:** "We want to be more empowered" (vague aspiration)
* **After:** "Our Team Structure scores 2/4 and Team Orchestration scores 1/4. We need to move from functional silos to cross-functional pods." (specific, measurable)

Key POM principles mapped:

| Principle           | Maps to                                       | What to look for                          |
| ------------------- | --------------------------------------------- | ----------------------------------------- |
| Empowered teams     | Team structure, team orchestration            | Are teams given problems, not features?   |
| Product discovery   | Strategic intelligence, customer intelligence | Do you continuously validate assumptions? |
| Outcome-driven      | Value proposition, product analytics          | Do you measure outcomes, not output?      |
| Continuous learning | Feedback loop, learn and compound             | Do you systematically learn from data?    |

## Building your diagnostic report

After running all three frameworks, synthesize findings into a diagnostic report for leadership.

### Structure

1. **Executive summary:** the cross-framework read (are the three frameworks aligned?) and top 3 systemic issues.
2. **Framework scores:** Team Operations composite, Lifecycle stage placement, Product Assessment composite. Show the tension map.
3. **Systemic gaps:** dimensions or stages weak across multiple frameworks.
4. **Recommended investments:** prioritized list of moves with projected impact.
5. **Benchmark context:** how your scores read against stage-appropriate peers.

<Tip>
  Ask DAC to help build this. On the scored product page, try: "Build me a diagnostic summary comparing my three frameworks for a leadership presentation."
</Tip>

## What's next

<CardGroup cols={2}>
  <Card title="Track your portfolio" icon="chart-mixed" href="/knowledge-base/leader-portfolio">
    Run diagnostics across multiple products and compare.
  </Card>

  <Card title="Set up agents" icon="robot" href="/knowledge-base/leader-agents">
    Automate diagnostic monitoring with scheduled agents.
  </Card>

  <Card title="Share with stakeholders" icon="share" href="/knowledge-base/founder-share">
    Package your diagnostic for board or investor conversations.
  </Card>

  <Card title="Benchmark your results" icon="scale-balanced" href="/knowledge-base/leader-benchmarks">
    Put your diagnostic in context with industry comparisons.
  </Card>
</CardGroup>