# Illustrative use cases

These scenarios explain potential use. They are **not** customer references, measured results, integration commitments, or delivery-time guarantees. Identify them as examples when you use them.

## Turn a product idea into a first usable version

Situation: A founder has an idea for a portal but needs to define the first meaningful version.

With Sphere: Discuss users and outcomes, make system context understandable, organize work into plans, and review implementation and verification as the product takes shape.

Limit: No fixed delivery time; scope and quality decisions remain.

## Add a feature that spans several components

Situation: Customers should track request status; the change may touch UI, services, and storage.

With Sphere: Treat the feature as one outcome, use the blueprint for relationships, connect work to plans, and evaluate combined behavior.

Limit: Exact systems and connections must be assessed for the project.

## Improve an existing internal tool

Situation: Staff struggle with a fragmented workflow.

With Sphere: Clarify friction and desired behavior, discuss affected areas, plan improvements, and review against staff needs.

Limit: Access and constraints influence what is practical.

## Carry a solution blueprint into implementation

Situation: An architect outlined a solution; handoffs keep losing context.

With Sphere: Shared blueprint and plans keep the relationship between the proposed solution and delivery work.

Limit: Not a promise that arbitrary diagrams import automatically.

## Continue work on a broader feature

Situation: Multiple related plans and revisions; the owner spends time prompting each next step.

With Sphere: Autoplay supports continued planning, implementation, and verification while reviewing progress and decisions that need attention.

Limit: Unresolved decisions, access limits, or unclear requirements can still stop progress.