Prodigent

Finding Who Owns What

Ownership is knowledge. When it is unclear, every change and every incident gets more expensive.

"Who owns this?" should be an easy question. In many organisations it is not. CODEOWNERS files drift. Team names change. The person with real expertise is not always the person listed as owner.

Separate ownership from expertise

Ownership

  • Accountable for the service
  • Handles prioritisation and ops
  • Should be unambiguous

Expertise

  • Deep understanding of behaviour
  • Often concentrated in a few people
  • Critical during incidents and redesigns
  • Record both - they are not the same signal.
  • Keep ownership attached to systems, not only to Slack memories.
  • Update ownership when teams reorganise, not months later.
  • Use incidents and changes as prompts to correct stale ownership.

Connect people to systems

Prodigent treats ownership and expertise as part of organisational knowledge, next to services and decisions.

Try Prodigent free