Skip to content

OJO PRODUCT EDUCATION / AGENT TEAM WORKFLOW

From a Fuzzy Idea to a Decision-Ready PRDTurn uncertainty into reviewable scope.

Use the OJO Product Requirements Strategist and a focused Skill sequence to clarify the user, evidence, positioning, priorities, non-goals, and first product scope before interface design begins.

OJO / PRODUCT EDUCATION04 DECISIONS
SKILL OR REVIEW METHOD

Steve Jobs Perspective + Product Requirements Analysis

Input
Idea, user, repeated problem, current workaround, and commercial goal.
Output
Problem framing, product promise, constraints, and research questions.
Human checkpoint
Is the team solving a repeated problem for a specific user?

Choose a stage to inspect the input, output, and human decision.

Inspect the artifacts and confirmation points that make a PRD useful.

THE PRODUCT DECISION

What must the team learn and decide before a product idea is ready for design and engineering review?

DIRECT. MAKE. REVIEW.

A useful PRD records decisions and uncertainty.

The goal is not to make an idea sound complete. The workflow should expose the user, evidence, priorities, non-goals, acceptance signals, and unanswered questions.

Your Agent Team applies the right Skills.

  1. 01

    01 / DISCOVERY

    Frame the user and repeated problem.

    Start with the real user, current behavior, workaround, commercial consequence, constraints, and the evidence already available.

    A product insight and positioning draft.

  2. 02

    02 / SCOPE

    Prioritize the first useful release.

    Separate must-have behavior from attractive additions. Record P0/P1/P2 features, non-goals, risks, dependencies, and the assumption each feature should test.

    A prioritized feature list and confirmed scope.

  3. 03

    03 / DOCUMENT

    Make the requirements reviewable.

    Translate accepted decisions into a PRD with requirements, acceptance signals, ownership, evidence gaps, and questions for design and engineering.

    A decision-ready PRD, not a claim that the idea is validated.

REQUIREMENTS STRATEGIST RECIPE

Move through evidence and confirmation—not directly from idea to document.

This recipe follows the current OJO product pipeline: analyze the product decision first, confirm scope, then structure the requirements for the next stage.

RECOMMENDED SEQUENCE

Move one reviewable artifact at a time.

  1. 01

    Frame

    Steve Jobs Perspective + Product Requirements Analysis

    Input
    Idea, user, repeated problem, current workaround, and commercial goal.
    Output
    Problem framing, product promise, constraints, and research questions.
    Review
    Is the team solving a repeated problem for a specific user?
  2. 02

    Research

    Competitive Analysis + evidence review

    Input
    Direct alternatives, adjacent products, user feedback, and internal evidence.
    Output
    A differentiated position and explicit evidence gaps.
    Review
    Which claims are observed, inferred, or still unknown?
  3. 03

    Prioritize

    Product Requirements Analysis + Prioritize Features

    Input
    Confirmed positioning, constraints, and risky assumptions.
    Output
    P0/P1/P2 features, non-goals, and acceptance signals.
    Review
    Does P0 create the smallest useful test of the product promise?
  4. 04

    Document

    Product Requirements Document

    Input
    Accepted scope and remaining questions.
    Output
    A reviewable PRD for design and engineering.
    Review
    Can each requirement trace to a user or business decision?

HUMAN REVIEW

Before moving forward

  • The target user and current behavior are specific.
  • Evidence and inference are visibly separated.
  • P0, non-goals, and constraints are explicit.
  • The PRD records open questions and ownership.

BOUNDARIES

What this workflow does not prove

  • AI-assisted competitive research can be incomplete or outdated and must be verified.
  • A PRD draft does not authorize roadmap, legal, security, or engineering commitments.
  • The next stage should revisit requirements when user evidence changes.

FROM CAPABILITY TO OUTCOME

Give the next team a question worth solving.

The PRD should help design and engineering challenge the product decision. Keep unresolved evidence visible so the document does not turn assumptions into facts.

  • Product insight and positioning
  • Prioritized first-release scope
  • PRD with open questions

PRODUCT QUESTIONS, ANSWERED

Before you assemble the team.

Can AI write a complete PRD from one sentence?

It can draft a document, but a useful PRD requires evidence, constraints, priorities, ownership, and human confirmation. Treat unsupported details as hypotheses.

What should I provide before starting?

Provide the target user, problem, business context, known evidence, alternatives, constraints, desired outcome, and any decisions the team has already made.

Where should the team stop and review?

Review after the positioning draft and again after the prioritized scope. Do not let the workflow silently turn a proposed feature list into an approved roadmap.

Does a decision-ready PRD mean the product is validated?

No. It means the decisions, assumptions, evidence, and next tests are clear enough for cross-functional review and subsequent validation.

BRING THE CAPABILITY INTO YOUR WORK

Make uncertainty visible.Give every requirement a reason.

Shape requirements in OJO

OJO brings product and business thinking, a design-aware Agent Team, specialist Skills, and thoughtful review into one workspace.