Create Cycle 1 : Situation Room

• Step1 : write a design brief based on :
• Problem Space:
  • elements with high relevance to problem
  • element relationships with high relevance to problem
  • An abstracted view–simplified to reveal the nature of the problem
  • Eliminate data that is noise to this problem
• Actors :
  • Internal Apps & Services, Vendors, Datasources, Users (ex: building apps that access AI on their machines), Team Members
• Flows / Dataflows:
  • Data moving from one source to another. meta data: Sensitivity (PII), origin, destination
• Borders
  • abstract or physical boundaries between actors. The boundaries used for data govenance.
• Remedy
  • Fix an issue within the problem space

Situation Room Page

The situation room focuses context on a problem space. The problem space can be free of problems. If there are problems, the room's priority becomes good at three things:

• The omnipresent good context
• Clarifying and visualizing the problem (New)
• Providing Remedies to the problem

State 1 - All the time:

• Problem space context, ex:
  • map of actors and dataflows (../qflow)
• state of the problem space (healthy, issues, anomaly)
• Health is actively shown
• Easy to zoom in and out to the relevant levels within the problem space
  • ex, wide–all at a glance: What is our company compliance
  • ex, narrow–deep focus: What data was sent to which vendor in X policy violation

State 2 - When we know there are problems to fix, let's surface them:

• Make it clear exactly what the problem is
• Which actors are involved
• Giving clear steps for fixing / remedy-ifing Example Remedies:
  • Talk to team, (ex: stop sending sensitive data)
  • Enforce the policy–Qcontrol
  • Reconfigure
  • Change the policy
  • Silence the alarm / extend grace
    • for period of time?

Ask any clarifying questions. Make suggestions or connections I may not have considered