Skip to content
Andrew Suprenant edited this page Dec 6, 2016 · 43 revisions

This documentation is a record of the research, findings, and principles that determine cloud.gov's strategic direction and its continuing decision-making process. It is a regularly-evolving framework for collecting, surfacing, and giving project context to these critical artifacts.

For more information on the how we manage and structure the cloud.gov project, see the cg-product README.md.


Overview

What’s the purpose of this documentation?

  • Why is this documentation here at all?
  • How can we use this documentation to make good decisions?

Who we are

Why cloud.gov exists

  • What's the context in which the cloud.gov project started?
  • What kind of problem do we exist to solve?

Market analysis

  • Who already exists in our market?
  • What distinguishes these existing options?

Users and needs

  • What kind of people and institutions use cloud.gov?
  • What do they expect from this service?

Core values, keywords, attributes

  • How do we describe ourselves?
  • What words or concepts are reflective of our values?

Mission statement

  • What do we do?
  • Who do we do it for?
  • What distinguishes this service?

Design principles

  • What concepts guide our building methods?
  • What are our design priorities?
  • How do these reflect our audience and core values?

Product roadmap and key features

  • What features are necessary to meet our users' needs?

Engineering principles

Anything to add here?


Interactive design

Style tiles

  • What's the visual inspiration for our product design?

Flows, Feedback, and Interaction

  • How do users interact with the product?
  • What high-level actions can users take, and how does the system handle these actions?

Information architecture

  • How do spatial arrangement and hierarchy communicate product functionality and messaging?

Wireframes/Prototypes

  • How can we visualize and test information architecture and interaction models?
  • How can we visualize and test new patterns and interactive motifs?

Framework

  • How do we build our products's font-end?

Pattern library

  • What are the blocks and components from which we build our product?
  • How do we implement these elements in our code?

Content design and house style

Anything to add here?

General content issues


Research

Experience of similar products (Date TK)

Troubleshooting an app (Date TK)

App usage and allocation (Date TK)

Competitive landscape


Published materials

Presentations

Blog posts

Fact sheets and 1-pagers

Clone this wiki locally