🖼️ See the drawing + lab 🏠 Course home 🌿 Branch on GitHub ✏️ View source

🖼️ आकृती आणि labThe drawing + lab पूर्ण पानावर उघडा ↗Open full page ↗

🤝 धडा 03 — Delegation आणि ownership: स्तर, RACI आणि bus factor

📍 तुम्ही इथे आहात: 12 पैकी धडा 03 · मागे: lesson-02-one-on-ones · पुढे: lesson-04-hiring

📦 या ब्रँचमध्ये काय आहे

धडा 02, आणि काम नीट सोपवणे. सात delegation levels ("मी तुला सांगते" पासून "तू ठरव" पर्यंत), RACI (कोण Responsible, Accountable, Consulted, Informed), आणि bus factor — एखाद्या कामाला करू शकणारे कोणीच उरणार नाही त्याआधी विभाग किती लोक गमावू शकतो. lead/demo.py मधले delegation(); lead/models.py मधले bus_factor(), raci_check() आणि DELEGATION.

🧒 5 वर्षांच्या मुलाला समजावल्यासारखे

कतरिना एक यादी लिहिते: गणित विभागातील प्रत्येक काम, आणि ते मदतीशिवाय कोण करू शकते. 📝

परीक्षा तपासणे: कतरिना, दीपिका, ऐश्वर्या. छान.
वेळापत्रक बनवणे: फक्त कतरिना.
परीक्षेच्या दिवसाचा आपत्कालीन आराखडा: फक्त कतरिना.

मग ती एक भीतीदायक प्रश्न विचारते: "परीक्षेच्या आठवड्यात मी आजारी पडले तर?" 🤒 दोन कामांसाठी कोणीच नसेल. ती संख्या — एखाद्या कामाला कोणीच उरण्याआधी किती लोक गैरहजर असू शकतात — म्हणजे bus factor. इथे तो 1 आहे. एक व्यक्ती गैरहजर, आणि विभाग अडकतो.

म्हणून कतरिना कामे सोपवू लागते. "माझ्यासाठी हा भाग कर" असे नाही, तर "हे आता तुझे आहे". दीपिका काही आठवडे कतरिनासोबत वेळापत्रक बनवते, मग एकटी. ऐश्वर्या परीक्षेच्या दिवसाचा आराखडा ताब्यात घेते. एका सत्रानंतर प्रत्येक कामासाठी किमान दोन जणी आहेत. Bus factor 2 आहे.

ती किती सोपवते आहे हे सांगायलाही ती शिकते: "तू ठरव, आणि नंतर मला सांग" हे "मला तुझी कल्पना सांग, आणि मी ठरवते" यापेक्षा खूप वेगळे आहे.

🗺️ आकृती

flowchart LR
    m["📝 who can do each job alone<br/>release: Katrina only<br/>runbooks: Katrina only"] --> b1["🚌 bus factor 1"]
    b1 -->|"a quarter of pairing"| p["🤝 Dipika runs releases<br/>Aishwarya owns runbooks<br/>Meera learns the database"]
    p --> b2["🚌 bus factor 2"]
    r["📋 RACI check<br/>weekly release: 2 accountable<br/>gradebook migration: 0 accountable"] --> f["✅ exactly one A,<br/>at least one R"]

🗺️ काढलेली आवृत्ती + एक lab: https://school-edh.pages.dev/engineering-leadership/lesson-diagrams.html#l03

❓ काय

Delegation — एखाद्याला फक्त पायऱ्यांची यादी नव्हे, तर परिणाम आणि तो गाठण्याचा अधिकार देणे. कसोटी: कामासाठी लागणारे निर्णय ती न विचारता घेऊ शकते का?
Delegation levels — Jurgen Appelo यांचे सात स्तर (Management 3.0 च्या "delegation poker" मधून): 1 tell (मी ठरवते आणि तुला सांगते) · 2 sell (मी ठरवते आणि का ते समजावते) · 3 consult (मी तुला विचारते, मग मी ठरवते) · 4 agree (आपण मिळून ठरवतो) · 5 advise (माझा सल्ला ऐकून तू ठरवतेस) · 6 inquire (तू ठरवतेस, मग मला सांगतेस) · 7 delegate (तू ठरवतेस; मला कळण्याची गरज नाही). स्तर मोठ्याने सांगितल्याने नेहमीचे अपयश टळते: तिला वाटले ती ठरवते आहे; तुम्हाला वाटले तुम्ही ठरवत आहात.
RACI — कामे × लोक यांचा तक्ता. Responsible: काम करते. Accountable: परिणामाची मालक आणि अंतिम निर्णय तिचा — प्रत्येक कामासाठी नेमका एकच. Consulted: आधी विचारले जाते. Informed: नंतर कळवले जाते. दोन A म्हणजे खरे तर कोणीच accountable नाही; शून्य A चा अर्थही तोच.
Bus factor ("truck factor" सुद्धा) — अशा लोकांची सर्वात लहान संख्या ज्यांच्या गैरहजेरीत एखादे आवश्यक कौशल्य कोणाकडेच उरणार नाही. या model मध्ये: कोणत्याही एका कौशल्याचे सर्वात कमी धारक. Bus factor 1 म्हणजे एका व्यक्तीपासून बनलेला single point of failure.
Skills matrix — लोक × कौशल्ये, प्रत्येकासाठी एक level (इथे 0–3). ही वाढीच्या आराखड्यांसाठी संवादाची सुरुवात आहे, performance score नाही.

🤔 का

कारण नवी lead सहसा टीममधील सर्वात कुशल व्यक्ती असते, म्हणून कोणतेही काम पूर्ण करायचा सर्वात जलद मार्ग म्हणजे ते स्वतः करणे. हे एक महिना चालते. मग प्रत्येक अवघड समस्या तिच्या दारात रांग लावते, ती सांभाळत असलेल्या systems टीम कधीच शिकत नाही, आणि तिची सुट्टी धोका बनते. Delegation मुळेच टीमची क्षमता lead च्या स्वतःच्या तासांच्या पलीकडे वाढते — आणि तेच संपूर्ण काम आहे (धडा 01). RACI आणि bus factor लपलेले single points दृश्य करतात.

🔧 कसे (या repo मध्ये)

lead/models.py मधले bus_factor(matrix, level=2) {person: {skill: 0..3}} घेते आणि प्रत्येक कौशल्याचे धारक (level किंवा त्यावरील लोक) आणि bus factor (सर्वात लहान धारक संख्या) परत देते. raci_check(raci) {task: {person: letters}} घेते आणि नेमका एक A नसलेले किंवा एकही R नसलेले प्रत्येक काम सूचीबद्ध करते. DELEGATION मध्ये Appelo यांचे सात स्तर आहेत. lead/demo.py मधले delegation() एका तिमाहीच्या pairing आधी आणि नंतरचा कतरिनाचा विभाग चालवते. Levels (0–3) हे स्वतः केलेले अंदाज आहेत: विचार करण्याचे साधन, माणसांसाठीचे सूत्र नाही.

🧪 करून पाहा

python3 lead/demo.py delegation
python3 - <<'EOF'
import sys; sys.path.insert(0, "lead"); from models import bus_factor, raci_check, DELEGATION
m = {"Katrina": {"gradebook": 3, "release": 3, "runbooks": 3},
     "Dipika": {"gradebook": 2, "release": 1, "runbooks": 1},
     "Aishwarya": {"gradebook": 2, "release": 0, "runbooks": 1}}
for level in (1, 2, 3):
    holders, bf = bus_factor(m, level)
    print(f"counting level {level}+ as 'can do it' → bus factor {bf} · release: {holders['release']}")
print(raci_check({"weekly release": {"Dipika": "RA", "Katrina": "C", "Aishwarya": "I"}}) or "RACI ok")
print(raci_check({"exam timetable": {"Katrina": "RA", "Dipika": "RA"}}))
print(" · ".join(DELEGATION))
EOF

✅ तपासा — तुम्हाला काय दिसायला हवे

delegation असे print करते:

   release    1 · Katrina
   runbooks   1 · Katrina
   bus factor 1 · if Katrina is out: ['release', 'runbooks'] have nobody
── after a quarter of pairing (Dipika runs releases, Aishwarya owns runbooks, Meera learns the database) → bus factor 2
── RACI check: weekly release: 2 accountable (Katrina, Dipika) · weekly release: nobody responsible · gradebook migration: 0 accountable (nobody)
   delegation level for 'which test framework the gradebook uses': 7 delegate
   delegation level for 'the exam-week release freeze': 4 agree
   delegation level for 'the hiring bar': 3 consult

तुमचा snippet असे print करतो:

counting level 1+ as 'can do it' → bus factor 2 · release: ['Katrina', 'Dipika']
counting level 2+ as 'can do it' → bus factor 1 · release: ['Katrina']
counting level 3+ as 'can do it' → bus factor 1 · release: ['Katrina']
RACI ok
['exam timetable: 2 accountable (Katrina, Dipika)']
1 tell · 2 sell · 3 consult · 4 agree · 5 advise · 6 inquire · 7 delegate

🏁 तुम्ही आत्ताच काय सिद्ध केले

Delegation आधी दोन कामांसाठी — release आणि runbooks — फक्त कतरिना होती, म्हणून bus factor 1 होता. एका तिमाहीच्या जाणीवपूर्वक pairing ने तो 2 केला. तुम्ही "करू शकते" म्हणून काय मोजता यावरही bus factor अवलंबून असतो: level 1 वर (मदतीने करू शकते) दीपिका releases साठी मोजली जाते आणि संख्या प्रत्यक्षापेक्षा जास्त निरोगी दिसते. RACI ने एका कामावर दोन A आणि दुसऱ्यावर एकही नाही हे पकडले — दोन्हींचा अर्थ "खरे तर कोणीच accountable नाही".

⚠️ नेहमीच्या चुका

काम सोपवणे पण निर्णय स्वतःकडे ठेवणे — ती काम करते आणि तरीही तुमची वाट पाहते
फक्त कंटाळवाणे काम सोपवणे, आणि रंजक समस्या स्वतःकडे ठेवणे
तुम्ही केले असते त्यापेक्षा वेगळ्या पद्धतीने पहिल्यांदाच झाले की काम परत घेणे
एकाच गोष्टीसाठी दोन व्यक्ती "accountable"
skills matrix ला लोकांची क्रमवारी समजणे
pairing ची पायरी वगळणे: handover शिवाय "हे आता तुझे आहे" म्हणजे सोडून देणे, delegation नव्हे

🏭 प्रत्यक्ष वापरात

टीमच्या docs मध्ये एक RACI तक्ता, प्रत्येक नियमित जबाबदारीसाठी एक row:

| Task                    | Katrina | Dipika | Aishwarya | Meera | Leela |
|-------------------------|---------|--------|-----------|-------|-------|
| Weekly release          | C       | A/R    | I         | R     | I     |
| Gradebook migration     | I       | A      | R         | C     | I     |
| Hiring loop             | A       | R      | R         | I     | I     |
| On-call runbooks        | C       | I      | A/R       | R     | I     |

Code मधील knowledge concentration चा ढोबळ संकेत: प्रत्येक भागात कोणी commit केले आहे. खऱ्या repository वर (हे commits मोजते, समज नव्हे — याचा वापर प्रश्न विचारण्यासाठी करा, लोकांचे मूल्यमापन करण्यासाठी नाही):

git shortlog -sn --since="12 months ago" -- services/gradebook/
git shortlog -sn --since="12 months ago" -- deploy/

CODEOWNERS file (GitHub आणि GitLab दोन्ही support करतात) ownership स्पष्ट करते, म्हणजे reviews एकापेक्षा जास्त व्यक्तींपर्यंत पोहोचतात:

/services/gradebook/   @school/maths-dipika @school/maths-aishwarya
/deploy/               @school/maths-dipika @school/maths-meera

🏭 प्रत्यक्ष वापरात हे का महत्त्वाचे आहे: तुम्ही दोन आठवडे दूर असाल तर बिघडतील अशा पाच गोष्टींची यादी करा. प्रत्येक गोष्ट म्हणजे तुम्ही अजून न केलेले delegation. एक निवडा, त्याचा स्तर सांगा, आणि या महिन्यात त्यावर pairing करा.

⏭️ पुढे

Delegation तुमच्याकडे असलेल्या लोकांमध्ये काम वाटते. लवकरच किंवा उशिरा तुम्हाला आणखी लोक लागतात — आणि hiring हा उलटायला महाग पडणाऱ्या मोजक्या निर्णयांपैकी एक आहे.

git checkout lesson-04-hiring

🤝 Lesson 03 — Delegation and ownership: levels, RACI and the bus factor

📍 You are here: Lesson 03 of 12 · Previous: lesson-02-one-on-ones · Next: lesson-04-hiring

📦 What's in this branch

Lesson 02, plus giving work away properly. The seven delegation levels (from "I tell you" to "you decide"), RACI (who is Responsible, Accountable, Consulted, Informed), and the bus factor — how many people the department can lose before some job has nobody who can do it. delegation() in lead/demo.py; bus_factor(), raci_check() and DELEGATION in lead/models.py.

🧒 Explain like I'm 5

Katrina writes a list: every job in the maths department, and who can do it without help. 📝

Marking exams: Katrina, Dipika, Aishwarya. Good.
Making the timetable: only Katrina.
The emergency plan for exam day: only Katrina.

Then she asks a scary question: "What if I am ill on exam week?" 🤒 Two jobs would have nobody. That number — how many people can be away before a job has nobody — is the bus factor. Here it is 1. One person away, and the department is stuck.

So Katrina starts giving jobs away. Not "do this bit for me", but "this is yours now". Dipika makes the timetable with Katrina for a few weeks, then alone. Aishwarya takes over the exam-day plan. After one term, every job has at least two people. The bus factor is 2.

She also learns to say how much she is giving away: "you decide, and tell me after" is very different from "tell me your idea, and I decide".

🗺️ Diagram

flowchart LR
    m["📝 who can do each job alone<br/>release: Katrina only<br/>runbooks: Katrina only"] --> b1["🚌 bus factor 1"]
    b1 -->|"a quarter of pairing"| p["🤝 Dipika runs releases<br/>Aishwarya owns runbooks<br/>Meera learns the database"]
    p --> b2["🚌 bus factor 2"]
    r["📋 RACI check<br/>weekly release: 2 accountable<br/>gradebook migration: 0 accountable"] --> f["✅ exactly one A,<br/>at least one R"]

🗺️ Drawn version + a lab: https://school-edh.pages.dev/engineering-leadership/lesson-diagrams.html#l03

❓ What

Delegation — giving someone the outcome and the authority to reach it, not just a list of steps. The test: can she make the decisions the work needs without asking?
Delegation levels — Jurgen Appelo's seven levels (from Management 3.0's "delegation poker"): 1 tell (I decide and tell you) · 2 sell (I decide and explain why) · 3 consult (I ask you, then I decide) · 4 agree (we decide together) · 5 advise (you decide after hearing my advice) · 6 inquire (you decide, then tell me) · 7 delegate (you decide; I do not need to know). Saying the level out loud avoids the classic failure: she thought she was deciding; you thought you were.
RACI — a table of tasks × people. Responsible: does the work. Accountable: owns the outcome and has the final say — exactly one per task. Consulted: asked before. Informed: told after. Two A's means nobody is really accountable; zero A's means the same.
Bus factor (also "truck factor") — the smallest number of people whose absence would leave some needed skill with nobody. In this model: the fewest holders of any one skill. A bus factor of 1 is a single point of failure made of a person.
Skills matrix — people × skills, with a level each (here 0–3). It is a conversation starter for growth plans, not a performance score.

🤔 Why

Because a new lead is usually the most skilled person on the team, so the fastest way to get anything done is to do it herself. That works for a month. Then every hard problem queues at her door, the team never learns the systems she holds, and her holiday becomes a risk. Delegation is how the team's capacity grows beyond the lead's own hours — which is the whole job (lesson 01). RACI and the bus factor make hidden single points visible.

🔧 How (in this repo)

bus_factor(matrix, level=2) in lead/models.py takes {person: {skill: 0..3}} and returns the holders of each skill (people at level or above) and the bus factor (the smallest holder count). raci_check(raci) takes {task: {person: letters}} and lists every task without exactly one A or without any R. DELEGATION holds Appelo's seven levels. delegation() in lead/demo.py runs Katrina's department before and after a quarter of pairing. The levels (0–3) are self-assessed guesses: a thinking tool, not a formula for people.

🧪 Try it

python3 lead/demo.py delegation
python3 - <<'EOF'
import sys; sys.path.insert(0, "lead"); from models import bus_factor, raci_check, DELEGATION
m = {"Katrina": {"gradebook": 3, "release": 3, "runbooks": 3},
     "Dipika": {"gradebook": 2, "release": 1, "runbooks": 1},
     "Aishwarya": {"gradebook": 2, "release": 0, "runbooks": 1}}
for level in (1, 2, 3):
    holders, bf = bus_factor(m, level)
    print(f"counting level {level}+ as 'can do it' → bus factor {bf} · release: {holders['release']}")
print(raci_check({"weekly release": {"Dipika": "RA", "Katrina": "C", "Aishwarya": "I"}}) or "RACI ok")
print(raci_check({"exam timetable": {"Katrina": "RA", "Dipika": "RA"}}))
print(" · ".join(DELEGATION))
EOF

✅ Verify — what you should see

delegation prints:

   release    1 · Katrina
   runbooks   1 · Katrina
   bus factor 1 · if Katrina is out: ['release', 'runbooks'] have nobody
── after a quarter of pairing (Dipika runs releases, Aishwarya owns runbooks, Meera learns the database) → bus factor 2
── RACI check: weekly release: 2 accountable (Katrina, Dipika) · weekly release: nobody responsible · gradebook migration: 0 accountable (nobody)
   delegation level for 'which test framework the gradebook uses': 7 delegate
   delegation level for 'the exam-week release freeze': 4 agree
   delegation level for 'the hiring bar': 3 consult

Your snippet prints:

counting level 1+ as 'can do it' → bus factor 2 · release: ['Katrina', 'Dipika']
counting level 2+ as 'can do it' → bus factor 1 · release: ['Katrina']
counting level 3+ as 'can do it' → bus factor 1 · release: ['Katrina']
RACI ok
['exam timetable: 2 accountable (Katrina, Dipika)']
1 tell · 2 sell · 3 consult · 4 agree · 5 advise · 6 inquire · 7 delegate

🏁 What you just proved

Before delegation, two jobs — release and runbooks — had only Katrina, so the bus factor was 1. A quarter of deliberate pairing raised it to 2. The bus factor also depends on what you count as "can do it": at level 1 (can do it with help) Dipika counts for releases and the number looks healthier than it is. RACI caught two A's on one task and none on another — both mean "nobody is really accountable".

⚠️ Common mistakes

delegating the task but keeping the decisions — she does the work and still waits for you
delegating only the dull work, and keeping the interesting problems
taking the work back the first time it is done differently from how you would do it
two people "accountable" for the same thing
treating the skills matrix as a ranking of people
skipping the pairing step: "it's yours now" with no handover is abandonment, not delegation

🏭 In production

A RACI table in the team's docs, one row per recurring responsibility:

| Task                    | Katrina | Dipika | Aishwarya | Meera | Leela |
|-------------------------|---------|--------|-----------|-------|-------|
| Weekly release          | C       | A/R    | I         | R     | I     |
| Gradebook migration     | I       | A      | R         | C     | I     |
| Hiring loop             | A       | R      | R         | I     | I     |
| On-call runbooks        | C       | I      | A/R       | R     | I     |

A rough signal of knowledge concentration in code: who has committed to each area. On a real repository (it counts commits, not understanding — use it to ask questions, not to judge people):

git shortlog -sn --since="12 months ago" -- services/gradebook/
git shortlog -sn --since="12 months ago" -- deploy/

A CODEOWNERS file (GitHub and GitLab support one) makes ownership explicit, so reviews reach more than one person:

/services/gradebook/   @school/maths-dipika @school/maths-aishwarya
/deploy/               @school/maths-dipika @school/maths-meera

🏭 Why this matters in production: list the five things that would break if you were away for two weeks. Each one is a delegation you have not made yet. Pick one, name its level, and pair on it this month.

⏭️ Next

Delegation spreads the work across the people you have. Sooner or later you need more people — and hiring is one of the few decisions that is expensive to undo.

git checkout lesson-04-hiring

← Previousone on ones Next →hiring

This page is the lesson's README from the lesson-03-delegation branch, shown here so the whole School stays on one site. Code files open on GitHub at the same branch.