Skip to content

Decision records

Julia Lindpaintner — she/her edited this page Feb 17, 2023 · 13 revisions

Decision records of all types

Content decision records

18F Guides content vision statement (Status: Accepted — 9/20/2022)

18F Guides content vision statement and exercise we used to produce it, based on this workshop (18F only 🔒)

Cross-discipline items (Status: Accepted — 11/14/2022)

For the current draft information architecture (18F only 🔒): Pull out categories that cross current Guide boundaries, but also make these available as a kind of index page — here are all the places you can learn about X.

Decision: for now, put aside the items that cross all parts of this work:

  • Accessibility
  • Ethics
  • Law
  • Principles Integrate them accordingly, but create an index for them later, and include a module on the side (or some such) to link to that index.

Context: Decision made due to seeing this come up as a problem for the Accessibility Guide also, as well as it coming up within the UX Guide (Ethics, etc.)

See additional content-related proposed decisions (18F only 🔒)

Design decision records

18F Guides design principles

Governance decision records

Accessibility for the Guides team (GSA only) contains accessibility approaches

Many other governance decisions are in the Guide to supporting 18F guides.

Terminology decision records

Our team agreed on language changes in our work together (original doc) (GSA only):

  • “Master” became “main” — commonly done across 18F teams at this point to avoid terminology associated with slavery and oppression
  • “North star” became “polestar” — the global south can’t see the north star
  • “Sprint” became “iteration” — we shouldn’t be sprinting all the time and not everyone can sprint
  • “Backlog grooming” became “backlog refinement” — “Grooming” as a term has gained stronger abuse connotations

Technical / architectural decision records

Technical and architectural decision records are documented in this GitHub repository.

How the team worked

Refer to the How we worked section, but Hello new team also provides an overview of how this team worked together best