Jeanne W. Ross’ Accountability Framework

I’ve been staring at this list:

  1. Component owners, not project managers
  2. Mission, not structure
  3. Metrics, not directives
  4. Experiments, not major launches
  5. Continuous releases, not scheduled releases
  6. Fully resourced teams, not matrixed functions
  7. Collaboration, not hierarchy
  8. Trust, not control

And wondering if a more dense way of saying it is instead:

  • Having a well-resourced, modern product management function to service the digital platform.
  • Ensure that “well-resourced” means having the right ratios of engineers and UX designers (combined with the right rituals) so that product edits/experiments can be continually released.