Skip to content

Check for alignment with the spirit and specifics of Teresa Torres perspective on OSTs #3

Closed

Description

@mindsocket

The schema bakes in a bunch of principles that I've not yet checked against "official" guidance on OSTs.

That might be ok, but it would help to work out the differences, decide which ones need addressing or documenting, and even consider if there's a strict vs relaxed or other "modes" (alt schemas).

Activity

  1. mindsocket commented on Feb 26, 2026

    @mindsocket
    OwnerAuthor

    Research complete. Full findings documented in docs/torres-alignment-research.md (including a reflection section with design decisions arising from the research).

    Summary of divergences from Torres' model

    Topic Torres Current schema Assessment
    Root node Single product metric ("desired outcome") Vision → Mission → Goal hierarchy Intentional extension — covers strategic context Torres considers out-of-scope
    Bottom layer Assumption tests Not present Gap — being addressed in #14 and #15
    Opportunity rules Customer-voiced, grounded in research, in problem space Free-form, no enforcement Hard to enforce structurally; descriptive rules (#16) and strict_ost schema (#15) address this
    Numeric assessments Not from Torres' model impact/feasibility/resources on opportunity/solution Reasonable pragmatic addition; excluded from strict_ost
    Solution parentage Opportunity only Opportunity or Solution Extension — sub-solutions not in Torres; excluded from strict_ost
    Terminology "assumption test" (not "experiment") Neither present Type aliases (#14) accept both

    Follow-up issues created

    Comments also added to #2, #5, #9, #10 with refinements from this research.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions