Mermaid Use Case Templates

Show users, the product, and external systems in one architecture overview.

Document the order of calls across frontend, gateway, services, and storage.

Explain how code moves from commit to production release.

Group application services by boundary and show directional dependencies.

Use C4-style syntax to explain people, systems, and major containers.

Clarify what happens after a domain event is published.

Show read-through cache logic with cache hits, misses, and refresh paths.

Map monitoring, alerts, on-call review, mitigation, and postmortem flow.

Describe a safe rollout lifecycle from internal testing to full release.

Model accounts, subscriptions, invoices, and payments for a SaaS product.

Document authors, posts, categories, and revisions.

Show customers, orders, line items, products, and shipments.

Explain fact tables, dimensions, events, and daily aggregates.

Model users, teams, roles, permissions, and assignments.

Track tickets, customers, agents, messages, and SLA events.

Represent devices, locations, sensor readings, and firmware versions.

Show learners, courses, lessons, enrollments, and completions.

Plan discovery, build, launch, and review phases for a quarter.

Create a lightweight sprint snapshot with todo, doing, review, and done.

Visualize dependencies and blockers before a release.

Rank project risks by impact and likelihood.

Communicate milestone order for planning or stakeholder updates.

Show how team effort is distributed across workstreams.

Describe how work moves through review gates before launch.

Show who receives updates during a project cycle.

Map signup, verification, first project, and activation.

Turn lead qualification into clear yes/no routing.

Document finance approval and exception handling.

Show how support tickets move through triage and escalation.

Explain request, vendor review, legal, security, and purchase order steps.

Coordinate HR, IT, manager, and finance tasks for offboarding.

Show how prospects move from traffic sources to conversion.

Document experience phases, user tasks, and satisfaction scores.

Show inspection, rework, approval, and shipment states.

Outline the main sections of an API documentation page.

Plan a developer-friendly README hierarchy.

Explain how architecture decision records move from proposal to accepted.

Guide readers from basics to advanced use.

Summarize product releases and notable changes over time.

Help readers debug a common product or integration issue.

Organize product terms, user roles, and core objects.

Show how source annotations become generated API reference pages.

Plan help center categories and subcategories.

Create an operational runbook for alerts and escalation.

Structure a product feature specification before implementation.

Show data ingestion, feature creation, model training, and evaluation.

Explain retrieval augmented generation from query to answer.

Document validation steps before data reaches analytics or ML.

Model feature sets, entities, versions, and training datasets.

Show the lifecycle of an ML or product experiment.

Visualize user event drop-off through an activation funnel.

Plan milestones for a data product launch.