Research Repository

A research repository should be

  • instantly searchable
  • citable
  • add value as a source of truth
  • accommodate multi-media
  • promote structured information
  • enable discovery
  • be a platform for researcher eminence
  • be a place to learn methods
  • be a tool for activating research
  • integrate into product planning
  • respect PII
  • provide tools to measure research usage
  • track research impact
  • have versioning
  • bi-directional linking
  • contextualize research alongside product data and company goals
  • allow expression of researchers' creativity and identities
  • push research to relevant stakeholders
  • be a graph
  • be a map
  • be a timeline
  • be an API for company insights
  • integrate into the tools where product teams work
  • be made up of small utilities over monoliths
  • save researchers time
  • create links between similar work
  • include data about stakeholders
  • be personalized to the user
  • be more like a water cooler than a filing cabinet
  • encourage peer review
  • encourage discourse
  • allow for different ways of working
  • be a fast utility
  • be whimsical
  • promote spaced repetition of findings
  • link out to roadmaps, org charts, planning docs, issues
  • be a compass pointings towards the social life of research
  • be local-first, if practical
  • be scrubbable peekable quicklook
  • search everything (reports, people, teams, methods, metadata)
  • make links to where you can see more
  • be mobile first
  • have arbitrary collections
  • have stable IDs/URLs