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

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

🗓️ धडा 01 — Engineer ते lead: आठवड्याचे तास कुठे जातात

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

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

हा संपूर्ण कोर्स एकाच बदलाबद्दल आहे: कतरिना शाळेतली सर्वोत्तम गणित शिक्षिका होती. आता ती गणित विभागप्रमुख आहे. तिच्या टीममध्ये दीपिका आणि ऐश्वर्या शिकवतात, आणि मीरा व लीला या दोन नव्या शिक्षिकाही आहेत. उत्तम धडा कसा शिकवायचा हे कतरिनाला अजूनही माहीत आहे — पण आता तिचे काम म्हणजे विभाग: कोण काय शिकवते, कोण अडकली आहे, कोण वाढते आहे, पालकांना काय वचन दिले होते. Engineering च्या भाषेत: ती engineer पासून engineering lead झाली. संपूर्ण कोर्सभर तुम्ही वापराल अशा खऱ्या files:

lead/models.py — मुख्याध्यापिकेचे कार्यालय छोट्या deterministic models च्या रूपात, शुद्ध Python मध्ये (zero dependencies)
lead/demo.py — प्रत्येक धडा एक छोटा program म्हणून (python3 lead/demo.py <section>; sections: calendar oneonones delegation hiring forecast priorities debt metrics topologies incidents writing growth)
lead/test_lead.py — models वरील 12 checks
demo-output.txt — निरोगी run काय print करतो

🎒 सुरू करण्याआधी: तुम्हाला फक्त Python 3 हवे, बाकी काही नाही. lead/ मधले प्रत्येक model विचार करण्याचे साधन आहे, माणसांसाठीचे सूत्र नाही: ते एक गृहीतक स्पष्ट दाखवते जेणेकरून तुम्ही त्यावर वाद घालू शकता. ते कोणत्याही व्यक्तीचे मोजमाप करत नाही, आणि त्याचा कोणताही threshold हा नियम नाही. जिथे संशोधन आहे तिथे धडे त्याचा काळजीपूर्वक उल्लेख करतात; जिथे नाही तिथे तसे स्पष्ट सांगतात.

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

कतरिना शिक्षिका होती तेव्हा तिचा आठवडा सोपा होता. शिकवायचे, तपासायचे, पुढच्या धड्याचे नियोजन करायचे. विचार करायला मोठे शांत तास. 📚

मग ती विभागप्रमुख झाली. आता दिवसभर लोक तिच्या दारावर ठोठावतात. 🚪 "परीक्षेबद्दल बोलूया का?" "लीला अडकली आहे." "पालकांना meeting हवी आहे."

सुरुवातीला कतरिना दोन्ही कामे करायचा प्रयत्न करते: तिचे जुने सगळे शिकवणे, आणि सगळे नवे बोलणे. ती उशिरापर्यंत थांबते. ती थकते. आणि तरीही विभागात गोंधळच वाटतो.

मग तिच्या लक्षात एक गोष्ट येते. तिच्या meetings दिवसभर विखुरलेल्या आहेत: एक 11 वाजता, एक 2 वाजता, एक 4 वाजता. त्यांच्या मध्ये फक्त छोट्या फटी उरतात — कोणत्याही अवघड गोष्टीवर विचार करायला खूप लहान. 🧩

म्हणून ती meetings एकत्र करते, दुपारी. Meetings तेवढ्याच. आता प्रत्येक सकाळ एक मोठा शांत तुकडा आहे. ☀️

आणि ती मोठी कल्पना स्वीकारते: तिचे काम आता ती शिकवते ते धडे राहिलेले नाही. तिचे काम म्हणजे संपूर्ण विभाग किती चांगले शिकवतो.

🗺️ आकृती

flowchart LR
    t["📚 teacher week<br/>meetings 5.0 h<br/>focus 30.5 h"] --> h["🏫 head of maths, scattered<br/>meetings 12.5 h<br/>focus 14.5 h · fragments 13.0 h"]
    h -->|"same meetings,<br/>moved to afternoons"| c["☀️ head of maths, clustered<br/>meetings 12.5 h<br/>focus 25.0 h · fragments 2.5 h"]
    c --> j["🎯 the job is now<br/>the department's output"]

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

❓ काय

Engineering lead / engineering manager — टीमच्या निकालांची आणि त्यातील लोकांची जबाबदारी असलेली व्यक्ती. कंपनीनुसार पदनामे खूप बदलतात ("tech lead", "team lead", "engineering manager"); काही भूमिका मुख्यतः technical असतात, काही मुख्यतः लोकांबद्दल. हा कोर्स त्यांपैकी बहुतेकांमध्ये समान असलेले भाग शिकवतो.
Managerial leverage — Andy Grove यांची High Output Management (1983) मधली कल्पना: manager चे output म्हणजे तिच्या टीमचे output, अधिक ती प्रभाव टाकते त्या टीम्सचे output. जी lead पाच जणींपैकी प्रत्येकीचे आठवड्याला दोन तास वाचवते, तिने दहा तास जोडले — स्वतः जलद coding करून ती जोडू शकली असती त्यापेक्षा जास्त.
Maker's schedule विरुद्ध manager's schedule — Paul Graham यांचा निबंध (2009). Makers (code लिहिणारे, design करणारे किंवा लेखन करणारे लोक) यांना मोठे अखंड तुकडे लागतात; सकाळच्या मध्येच एक meeting संपूर्ण सकाळ खाऊ शकते. Managers एक-एक तासाच्या slots मध्ये काम करतात. Lead एकाच वेळी दोन्ही schedules वर जगते.
Focus time — या lab मध्ये: किमान 2 तासांच्या तुकड्यांमध्ये मिळणारा मोकळा वेळ (तुम्ही हे बदलू शकता). Fragments — लहान तुकड्यांतील मोकळा वेळ. मोकळे तास तेवढेच असूनही ते बहुतेक focus असू शकतात किंवा बहुतेक fragments.
Player-coach trap — जुने engineering काम पूर्ण आकारात ठेवून त्यावर lead चे काम जोडणे. याचा अर्थ सहसा असा होतो की lead चे काम — 1:1s, planning, अडथळे दूर करणे — हेच वगळले जाते, आणि टीम lead च्या code reviews ची वाट पाहत बसते.

🤔 का

कारण नव्या lead साठी सर्वात आधी बदलते ते म्हणजे calendar, आणि हे कोणी सांगत नाही. Meetings विखुरलेल्या slots मध्ये येतात. अवघड विचाराचे काम (design review, hiring चा आराखडा, एखादा कठीण संदेश) यासाठी मोठे तुकडे लागतात. निर्णय घेतला नाही तर आठवडा आधी विचारणारा भरून टाकतो. आठवड्याकडे data म्हणून पाहणे — प्रकारानुसार तास, focus विरुद्ध fragments — "मी व्यस्त आहे" याचे रूपांतर तुम्ही घेऊ शकता अशा निवडींमध्ये करते.

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

lead/models.py मधले week(meetings, min_block_h=2.0) meetings ची यादी — (day, "HH:MM", minutes, kind) — 09:00–17:00 च्या पाच दिवसांवर अर्ध्या तासाच्या slots मध्ये मांडते. ते प्रकारानुसार meeting तास, मोकळे तास, focus तास (किमान min_block_h चे मोकळे सलग तुकडे), focus blocks ची संख्या, आणि fragments (उरलेला मोकळा वेळ) परत देते. lead/demo.py मधले calendar() तीन आठवड्यांची तुलना करते: शिक्षिका म्हणून कतरिना, विखुरलेल्या meetings असलेली नवी विभागप्रमुख, आणि त्याच meetings दुपारी एकत्र केलेली विभागप्रमुख. हे विचार करण्याचे साधन आहे, माणसांसाठीचे सूत्र नाही: खऱ्या आठवड्यांमध्ये प्रवास, व्यत्यय आणि chat messages असतात जे model ला दिसत नाहीत.

🧪 करून पाहा

python3 lead/demo.py calendar
python3 - <<'EOF'
import sys; sys.path.insert(0, "lead"); from models import week
days = ("Mon", "Tue", "Wed", "Thu", "Fri")
daily = [(d, "09:30", 30, "standup") for d in days]
cals = {"no meetings at all": [],
        "daily standup at 09:30": daily,
        "standup moved to 12:30": [(d, "12:30", 30, "standup") for d in days],
        "09:30 standup + a 1:1 at 11:00 daily": daily + [(d, "11:00", 30, "1:1") for d in days],
        "09:30 standup + a 1:1 at 10:00 daily": daily + [(d, "10:00", 30, "1:1") for d in days]}
for label, cal in cals.items():
    w = week(cal)
    print(f"{label:<37} meetings {w['meetings']:>4.1f} h · focus {w['focus']:>4.1f} h · fragments {w['fragments']:>4.1f} h")
lead = daily + [(d, "11:00", 30, "1:1") for d in days] + [(d, "14:00", 60, "sync") for d in days]
for block in (1.0, 2.0, 3.0):
    w = week(lead, min_block_h=block)
    print(f"a scattered lead week, focus needs {block:.0f} h+ → focus {w['focus']:>4.1f} h in {w['blocks']:>2} blocks")
EOF
python3 lead/test_lead.py

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

calendar असे print करते:

   as a teacher (engineer)      meetings  5.0 h · free 35.0 h · focus 30.5 h in  6 blocks · fragments  4.5 h
   as head of maths, scattered  meetings 12.5 h · free 27.5 h · focus 14.5 h in  6 blocks · fragments 13.0 h
   as head of maths, clustered  meetings 12.5 h · free 27.5 h · focus 25.0 h in 10 blocks · fragments  2.5 h
   the lead's meetings by kind: standup 2.5 h · 1:1 2.5 h · planning 1 h · hiring 2 h · sync 1 h · review 2 h · roadmap 1.5 h

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

no meetings at all                    meetings  0.0 h · focus 40.0 h · fragments  0.0 h
daily standup at 09:30                meetings  2.5 h · focus 35.0 h · fragments  2.5 h
standup moved to 12:30                meetings  2.5 h · focus 37.5 h · fragments  0.0 h
09:30 standup + a 1:1 at 11:00 daily  meetings  5.0 h · focus 27.5 h · fragments  7.5 h
09:30 standup + a 1:1 at 10:00 daily  meetings  5.0 h · focus 32.5 h · fragments  2.5 h
a scattered lead week, focus needs 1 h+ → focus 27.5 h in 15 blocks
a scattered lead week, focus needs 2 h+ → focus 22.5 h in 10 blocks
a scattered lead week, focus needs 3 h+ → focus  0.0 h in  0 blocks

Tests शेवटी 12/12 passed दाखवतात.

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

नव्या विभागप्रमुखाच्या 12.5 तास meetings आहेत, आणि फक्त त्यामुळे तिचा मोकळा वेळ 35 वरून 27.5 तासांवर येतो. पण meetings कुठे बसतात हेही जवळपास तितकेच महत्त्वाचे आहे: विखुरलेल्या असताना त्या मोकळ्या वेळापैकी फक्त 14.5 तास 2 तासांच्या तुकड्यांत मिळतात; दुपारी एकत्र केल्यावर त्याच meetings 25.0 तास focus सोडतात. रोजची एक 1:1 11:00 वरून 10:00 वर — standup च्या शेजारी — हलवल्याने 7.5 तासांचे fragments पुन्हा 2.5 वर येतात. आणि तुमच्या अवघड कामाला 3 तासांचे तुकडे लागत असतील, तर थोडासा विखुरलेला आठवडाही एकही तुकडा सोडू शकत नाही.

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

जुने engineering काम पूर्ण आकारात ठेवणे, आणि lead चे काम संध्याकाळी करणे
टीमचे सर्वात तातडीचे किंवा सर्वात रंजक technical काम स्वतः घेणे — तुम्हीच bottleneck बनता
प्रत्येक meeting मिळेल त्या slot मध्ये स्वीकारणे
तुम्ही किती code ship केला यावरून तुमचा आठवडा मोजणे
तुम्ही जसे तुमचे calendar पाहता तसेच टीम पाहते असे गृहीत धरणे — तुम्ही कधी उपलब्ध आहात आणि कधी नाही हे मोठ्याने सांगा

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

काहीही बदलण्याआधी तुमच्या calendar चा एक खरा महिना पाहा. अनेक calendar apps .ics मध्ये export करू शकतात; काही ओळी त्याचे प्रकारानुसार तासांत रूपांतर करतात. खऱ्या account वर (तुमच्या स्वतःच्या calendar export वर):

grep -c "BEGIN:VEVENT" my-calendar.ics          # how many meetings last month

मग एक छोटी calendar policy लिहा आणि टीमसोबत share करा:

Katrina's week (head of maths)
- Mornings Mon–Thu 10:00–13:00: focus time. Pull me out for incidents and people problems only.
- 1:1s: Mon and Tue afternoons, same slot every week.
- Office hours: Wed 15:00–16:00, no agenda needed.
- If you need a decision from me, write it down first (lesson 11) — I answer within a day.

अनेक टीम्स सगळ्यांसाठी meeting-free blocks वरही सहमती करतात (उदाहरणार्थ, meeting नसलेली एक दुपार). याचा नेमका किती फायदा होतो याचे पुरावे मिश्र आहेत आणि बहुतेक स्वतः सांगितलेले आहेत, म्हणून याला प्रयोग समजा: एक महिना करून पाहा, मग टीमला विचारा.

🏭 प्रत्यक्ष वापरात हे का महत्त्वाचे आहे: नव्या lead ची पहिली तिमाही तिच्या सवयी ठरवते. तुमचे तास कुठे जातात ते लिहून ठेवा, काय करणे थांबवायचे ते ठरवा, आणि काही maker blocks जाणीवपूर्वक जपा — नेतृत्वाचे विचाराचे काम तिथेच होते.

⏭️ पुढे

त्या calendar मधल्या सर्वात महत्त्वाच्या meetings लहान असतात: 1:1s, आणि त्यात होणारा feedback.

git checkout lesson-02-one-on-ones

🗓️ Lesson 01 — From engineer to lead: where the week's hours go

📍 You are here: Lesson 01 of 12 · Next: lesson-02-one-on-ones

📦 What's in this branch

The one change this whole course is about: Katrina was the best maths teacher in the school. Now she is head of the maths department. Dipika and Aishwarya teach in her team, with two newer teachers, Meera and Leela. Katrina still knows how to teach a great lesson — but her job is now the department: who teaches what, who is stuck, who is growing, what the parents were promised. In engineering words: she went from engineer to engineering lead. Real files you will use all the way through:

lead/models.py — the head teacher's office as small deterministic models, in pure Python (zero dependencies)
lead/demo.py — every lesson as a small program (python3 lead/demo.py <section>; sections: calendar oneonones delegation hiring forecast priorities debt metrics topologies incidents writing growth)
lead/test_lead.py — 12 checks on the models
demo-output.txt — what a healthy run prints

🎒 Before you start: you need Python 3 and nothing else. Every model in lead/ is a thinking tool, not a formula for people: it makes one assumption visible so you can argue with it. It does not measure a person, and none of its thresholds is a law. Where research exists the lessons name it carefully; where it does not, they say so.

🧒 Explain like I'm 5

When Katrina was a teacher, her week was simple. Teach, mark, plan the next lesson. Long quiet hours to think. 📚

Then she became head of the department. Now people knock on her door all day. 🚪 "Can we talk about the exam?" "Leela is stuck." "The parents want a meeting."

At first Katrina tries to do both jobs: all her old teaching, plus all the new talking. She stays late. She is tired. And the department still feels messy.

Then she notices something. Her meetings are spread all over the day: one at 11, one at 2, one at 4. Between them there are only small gaps — too short to think about anything hard. 🧩

So she moves the meetings together, into the afternoons. The same number of meetings. Now every morning is one long quiet block. ☀️

And she accepts the big idea: her work is no longer the lessons she teaches. Her work is how well the whole department teaches.

🗺️ Diagram

flowchart LR
    t["📚 teacher week<br/>meetings 5.0 h<br/>focus 30.5 h"] --> h["🏫 head of maths, scattered<br/>meetings 12.5 h<br/>focus 14.5 h · fragments 13.0 h"]
    h -->|"same meetings,<br/>moved to afternoons"| c["☀️ head of maths, clustered<br/>meetings 12.5 h<br/>focus 25.0 h · fragments 2.5 h"]
    c --> j["🎯 the job is now<br/>the department's output"]

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

❓ What

Engineering lead / engineering manager — the person responsible for a team's results and for the people in it. Titles vary a lot between companies ("tech lead", "team lead", "engineering manager"); some roles are mostly technical, some mostly people. This course covers the parts most of them share.
Managerial leverage — Andy Grove's idea in High Output Management (1983): a manager's output is the output of her team, plus the teams she influences. A lead who saves each of five people two hours a week has added ten hours — more than she could by coding faster herself.
Maker's schedule vs manager's schedule — Paul Graham's essay (2009). Makers (people who write code, or design, or write) need long unbroken blocks; one meeting in the middle of a morning can cost the whole morning. Managers work in one-hour slots. A lead lives on both schedules at once.
Focus time — in this lab: free time that comes in blocks of at least 2 hours (you can change that). Fragments — free time in shorter pieces. The same number of free hours can be mostly focus or mostly fragments.
The player-coach trap — keeping your old engineering job at full size and adding the lead job on top. It usually means the lead work — 1:1s, planning, unblocking — is what gets skipped, and the team waits on the lead's code reviews.

🤔 Why

Because the first thing that changes for a new lead is the calendar, and nobody tells you. Meetings arrive in scattered slots. The hard thinking work (a design review, a hiring plan, a difficult message) needs long blocks. Without a decision, the week is filled by whoever asks first. Looking at the week as data — hours by kind, focus vs fragments — turns "I am busy" into choices you can make.

🔧 How (in this repo)

week(meetings, min_block_h=2.0) in lead/models.py lays a list of meetings — (day, "HH:MM", minutes, kind) — onto five days of 09:00–17:00 in half-hour slots. It returns meeting hours by kind, free hours, focus hours (free runs of at least min_block_h), the number of focus blocks, and fragments (the rest of the free time). calendar() in lead/demo.py compares three weeks: Katrina as a teacher, as a new head with scattered meetings, and as a head with the same meetings clustered into the afternoons. This is a thinking tool, not a formula for people: real weeks have travel, interruptions and chat messages that the model does not see.

🧪 Try it

python3 lead/demo.py calendar
python3 - <<'EOF'
import sys; sys.path.insert(0, "lead"); from models import week
days = ("Mon", "Tue", "Wed", "Thu", "Fri")
daily = [(d, "09:30", 30, "standup") for d in days]
cals = {"no meetings at all": [],
        "daily standup at 09:30": daily,
        "standup moved to 12:30": [(d, "12:30", 30, "standup") for d in days],
        "09:30 standup + a 1:1 at 11:00 daily": daily + [(d, "11:00", 30, "1:1") for d in days],
        "09:30 standup + a 1:1 at 10:00 daily": daily + [(d, "10:00", 30, "1:1") for d in days]}
for label, cal in cals.items():
    w = week(cal)
    print(f"{label:<37} meetings {w['meetings']:>4.1f} h · focus {w['focus']:>4.1f} h · fragments {w['fragments']:>4.1f} h")
lead = daily + [(d, "11:00", 30, "1:1") for d in days] + [(d, "14:00", 60, "sync") for d in days]
for block in (1.0, 2.0, 3.0):
    w = week(lead, min_block_h=block)
    print(f"a scattered lead week, focus needs {block:.0f} h+ → focus {w['focus']:>4.1f} h in {w['blocks']:>2} blocks")
EOF
python3 lead/test_lead.py

✅ Verify — what you should see

calendar prints:

   as a teacher (engineer)      meetings  5.0 h · free 35.0 h · focus 30.5 h in  6 blocks · fragments  4.5 h
   as head of maths, scattered  meetings 12.5 h · free 27.5 h · focus 14.5 h in  6 blocks · fragments 13.0 h
   as head of maths, clustered  meetings 12.5 h · free 27.5 h · focus 25.0 h in 10 blocks · fragments  2.5 h
   the lead's meetings by kind: standup 2.5 h · 1:1 2.5 h · planning 1 h · hiring 2 h · sync 1 h · review 2 h · roadmap 1.5 h

Your snippet prints:

no meetings at all                    meetings  0.0 h · focus 40.0 h · fragments  0.0 h
daily standup at 09:30                meetings  2.5 h · focus 35.0 h · fragments  2.5 h
standup moved to 12:30                meetings  2.5 h · focus 37.5 h · fragments  0.0 h
09:30 standup + a 1:1 at 11:00 daily  meetings  5.0 h · focus 27.5 h · fragments  7.5 h
09:30 standup + a 1:1 at 10:00 daily  meetings  5.0 h · focus 32.5 h · fragments  2.5 h
a scattered lead week, focus needs 1 h+ → focus 27.5 h in 15 blocks
a scattered lead week, focus needs 2 h+ → focus 22.5 h in 10 blocks
a scattered lead week, focus needs 3 h+ → focus  0.0 h in  0 blocks

The tests end with 12/12 passed.

🏁 What you just proved

The new head has 12.5 hours of meetings, and that alone cuts her free time from 35 to 27.5 hours. But where the meetings sit matters almost as much: scattered, only 14.5 hours of that free time comes in 2-hour blocks; clustered in the afternoons, the same meetings leave 25.0 hours of focus. Moving one daily 1:1 from 11:00 to 10:00 — next to the standup — turns 7.5 hours of fragments back into 2.5. And if your hard work needs 3-hour blocks, a lightly scattered week can leave none.

⚠️ Common mistakes

keeping your old engineering workload at full size, and doing the lead job in the evenings
taking the team's most urgent or most interesting technical work yourself — you become the bottleneck
accepting every meeting in whatever slot it is offered
measuring your week by how much code you shipped
assuming the team sees your calendar the way you do — say out loud when you are and are not available

🏭 In production

Look at a real month of your calendar before you change anything. Many calendar apps can export to .ics; a few lines turn that into hours per kind. On a real account (your own calendar export):

grep -c "BEGIN:VEVENT" my-calendar.ics          # how many meetings last month

Then write a short calendar policy and share it with the team:

Katrina's week (head of maths)
- Mornings Mon–Thu 10:00–13:00: focus time. Pull me out for incidents and people problems only.
- 1:1s: Mon and Tue afternoons, same slot every week.
- Office hours: Wed 15:00–16:00, no agenda needed.
- If you need a decision from me, write it down first (lesson 11) — I answer within a day.

Many teams also agree on meeting-free blocks for everyone (a no-meeting afternoon, for example). Evidence on exactly how much this helps is mixed and mostly self-reported, so treat it as an experiment: try it for a month, then ask the team.

🏭 Why this matters in production: a new lead's first quarter decides her habits. Write down where your hours go, decide what you will stop doing, and protect a few maker blocks on purpose — they are where the thinking work of leading happens.

⏭️ Next

The most important meetings in that calendar are the small ones: 1:1s, and the feedback that happens in them.

git checkout lesson-02-one-on-ones

← Course homeall lessons Next →one on ones

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