Opine
  • Welcome to Opine
  • Key concepts
  • Guides
    • Getting started
      • Account setup
      • Connect your tools
      • Product tour
        • Workbench
        • Deals
        • Plans
        • Plan Templates
        • Criteria Library
        • Requests
      • Conclusion
    • How to run your first evaluation
      • Create a plan
      • Customize the plan
      • Connect Slack channels
      • Share the Plan
      • Track Plan progress
      • Use Opine AI
      • AI Document Generation
    • How to set your team up for success with the Library
      • Defining Success Criteria
      • Building your Library
      • Creating Templates
      • Creating Plays
      • Criteria Metrics
      • Conclusion
  • Security
    • SAML
  • Integrations
    • Clari
    • Gong
    • Google Calendar
    • HubSpot
    • Jira
    • Linear
    • Salesforce
    • Slack
    • Microsoft Teams
    • Zoom
  • API
    • Overview
    • API Reference
      • Deals
      • Evaluations
      • Invitations
      • Organization
      • Users
Powered by GitBook
On this page
  • Start with your most frequently tested capabilities
  • Keep Success Criteria modular and composable
  • Use labels to drive consistency and discoverability
  • Set up a review rhythm
  1. Guides
  2. How to set your team up for success with the Library

Building your Library

PreviousDefining Success CriteriaNextCreating Templates

Last updated 1 month ago

Once you’ve started adding Success Criteria, the next step is making sure they stay usable, discoverable, and trustworthy as your team—and your evaluation volume—grows.

Here’s how to structure and manage your library so it remains a scalable asset, not a cluttered checklist.


Start with your most frequently tested capabilities

Don’t aim to document everything at once. Instead, focus on the capabilities that show up most often in evaluations—these are your “core” Success Criteria. Common examples include:

  • Integration readiness (e.g., Salesforce, SSO, SIEM exports)

  • Security and compliance (e.g., audit logging, role-based access control)

  • Performance or SLAs (e.g., data refresh rates, latency benchmarks)

These recurring patterns will quickly deliver value through reuse and help establish your baseline for what “evaluation-ready” means at your company.


Keep Success Criteria modular and composable

Each Criterion should describe one distinct, testable capability. That makes it easier to mix and match them across Plan Templates and Plays. Avoid bundling multiple concepts (e.g., “Access control and audit logging”) into one.

Smaller, focused Criteria improve clarity for buyers and help your team tailor plans more precisely.


Use labels to drive consistency and discoverability

A clean, consistent labeling strategy makes your library faster to navigate—and ensures newer team members can find what they need. Consider aligning your labels to:

  • Product areas: Security, Integrations, Analytics

  • Use case types: Internal Only, Buyer-Specific, Critical

  • Segments or verticals: Enterprise, Healthcare, GovCloud

As your library grows, these labels become invaluable for filtering and building Plan Templates on the fly.


Set up a review rhythm

Treat your Success Criteria like product documentation: they need ownership and periodic review. We recommend:

  • Assigning a clear owner for each major category (e.g., security, integrations, core product)

  • Reviewing top-used Criteria quarterly for accuracy and buyer feedback

  • Archiving or consolidating outdated or duplicate entries

With the right structure and habits in place, your Criteria Library becomes a strategic advantage—not just a checklist.

Up next, we’ll look at how to turn your Criteria Library into repeatable, scalable workflows using Plan Templates.