🛠️ #transparency Things, Metrics, & Widgets
 A “bi” approach to the org
 


Things & Metrics


Guide

Type = 2 types, either a Metric (essentially, a numeric), or a Thing (a piece of content, which could also be counted as a “Metric”). “We want to count” calls out specific “things” we should also think of as metrics. 

Status: Exec: is something we want to at least, conceptually, show on the “home screen,” Primary: are key items which typically populate “drill in screens,” Secondary: are items that are 

Browse depth: (applies to things only) Short: Minimal amount of info, no real content. Medium: Scannable amount of info. Deep: meaningful engagement, asking the reader to refer to an outline and see immersive content.


Notes:
  • We will need a project named ORG, as well as one for COMMs, will prob be treated a wildcard.
  • Anonymous feedback should stay… anonymous, and perhaps not broadcasted to a team.


Widgets

TK





Related


Hierarchy of the ORG by Camellia (intended to almost be a visual)

  • Countdown — to Inforum, in days. 
  • Milestones & Releases — each major project will have a number of these. Each milestone can have not started/in-progress/complete status
  • Reach & Resourcing — how many Infor solutions touched by H&L and time invested by team. 
  • Suggest a weekly area chart with granularity of 1/2 looper week. (ie: each person can have up to 2 half-weeks to Infor solutions, could be collected via Polly)
  • OKRs — these are mostly qualitative and cross-functional. So I think the best way to report on their status is a simple green/yellow/red. 
 
more:
​+Hook & Loop—Experience R&D​ 
​+Hook & Loop—Working Models​Â