Skip to content

[Positioning] PM Decision — Primary audience persona #69

Description

Decision needed

Who is the primary user of this MCP server?

Candidates:

  • (A) Developers building AI agents/apps on Azure DocumentDB.
  • (B) Data engineers / ops doing AI-assisted data exploration.
  • (C) DBAs doing routine ops.
  • (D) Any DocumentDB user.

Why this matters

Without a named primary persona (and named non-audiences), every feature request gets weighed against five competing users and nothing ships.

Recommendation

(A) primary, (B) secondary. Not (C), not (D).

  • (C) is better served by Compass, mongosh, the Azure portal.
  • (D) is too broad — every feature is a trade-off; we need to know whose trade-off we're optimizing.

Acceptance criteria

  • Personas documented in docs/audiences.md or README.
  • Decision used to triage feature requests going forward.
  • Comparison page references the chosen audience.

Blocks

Several positioning artifacts (comparison table, Use this when section, personas page).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

decisionNeeds PM/leadership decisionpositioningProduct positioning & messagingtier-1Highest priority - ship before GA

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions