He does not personally have to make all decisions, or write all code, or do all releases. He is typically a squad member or chapter lead who has other day-to-day responsibilities in addition to the system ownership. However, from time to time he will take a “system owner day” and do housekeeping work on that system. Normally we try to keep this system ownership to less than a tenth of a person’s time.
5
5 reads
The idea is part of this collection:
Learn more about motivationandinspiration with this collection
Effective note-taking techniques
Test-taking strategies
How to create a study schedule
Related collections
Similar ideas to The System Owner is not a bottleneck or ivory tower architect
All systems have a system owner, or a pair of system owners (we encourage pairing). For operationally critical systems, the System Owner is a Dev-Ops pair – that is, one person with a developer perspective and one person with an operations perspective.
The system owner is the “go-to...
Our ancestors walked about 5 miles a day - or about 10,000 steps. Many people are moving less than they did before the pandemic. If 10,000 steps feel too out of reach, it's OK. It doesn't really matter what you do, as long as you're focused on movement.
In villages in remote parts of the w...
If a newbie starts working deeply, he will not be working as deeply and for as long a time period as someone who’s been doing deep work for many months or years.
Don’t expect to be able to work deeply for hours on end in the beginning. You might only have the concentration and energy to do ...
Read & Learn
20x Faster
without
deepstash
with
deepstash
with
deepstash
Personalized microlearning
—
100+ Learning Journeys
—
Access to 200,000+ ideas
—
Access to the mobile app
—
Unlimited idea saving
—
—
Unlimited history
—
—
Unlimited listening to ideas
—
—
Downloading & offline access
—
—
Supercharge your mind with one idea per day
Enter your email and spend 1 minute every day to learn something new.
I agree to receive email updates