How-To Videos

Stakeholder Roles

Stakeholder Map

Origo account provisioning Process

Product Team: Defines Jurisdiction & Uploads Data Model

Product Team, Legal Team, Activists, researchers: Uploads source & Selects References For Context

Primary User Flow: Creating a Protocol

Secondary User Flow: Tagging a data model

Primary User Flow: Managing Legally Operative Terms at Scale

Primary User Flow: Tagging a data model

Primary User Flow: Executing on Protocol / Requirement

Primary User Flow: Coordination and Managed Chaos

Design Drill-down: Data Model

Future Campaign Strategy

Incorporating the experience of activists and researchers is part of next steps.

Future structural and internal-local user stories:

Product team, lawyers, and legislators shall be able to view references from activists and researchers so that they can understand what is urgent and meaningful to the public.
Product team, lawyers, and legislators shall be able to view votes on references from activists and researchers so that they can dimension what matters to the public.

Future internal-global user stories:

Activists, researchers, and the general public shall be able to view implemented protocols in a scannable checklist / summarized grade so they can make informed purchasing decisions.
Activists, researchers, and the general public shall be able to drill down into implemented protocols to learn about technical specifications for software so that they can be educated on software and software development.
Activists and researchers shall be able to upload and annotate references that will automatically be sent to relevant product teams.

‍

In deciding which problems are relevant, the social groups concerned with the artifact and the meanings that those groups give to the artifact play a crucial role: a problem is defined as such only when there is a social group for which it constitutes a "problem."
Trevor J. Pinch & Wiebe E. Bijker
The Social Construction of Facts and Artifacts

These roles were informed through numerous semi-structured interviews across multiple domains. Each role was built off at least five participants, with the exception of the speculative lawyer who was designed to fit the needs of the problem space.

The product architecture and user flows were built around these roles. As such, they structure the product. However, they were also assumed to be fluid to reflect the nature of roles as typically found in a start-up environment. Thus, while they each structure the product experience, no role has a specific tailored experience. Instead, the platform is split into spaces: structural, local-internal, and local-external. These spaces mediate and ground the experience while ensuring that roles are not over-constrained and personal freedom for each role is preserved.