AI ke Daur Mein Sochna: 90-Minute Crash Course
6 Disciplines - 6 AI Failure Modes - Aik Rule
Monday subah do log aik hi AI tool kholte hain. Task bhi same hai: decide karna ke un ki company ko senior strategy lead hire karna chahiye, ya wohi paisa licenses, infrastructure, aur design time mein laga kar AI workforce banani chahiye jo har existing consultant ki capacity barha de. Dono ke paas Claude, ChatGPT, aur Gemini ka access hai. Dono ke paas decide karne ke liye aik hi hafta hai.
Person A Friday ko defensible recommendation ke saath finish karti hai: har claim ka documented record jo us ne accept ya reject kiya, aur teen reversal triggers jin par board usay baad mein hold kar sakta hai. Person B Friday ko polished memo ke saath finish karta hai jo zyada tar wahi analysis repeat karta hai jo AI ne Monday ko diya tha, aur jab CFO poochta hai ke paragraph four yahan kyun land hua to us ke paas jawab nahin hota.
Tools same. Problem same. Outcomes different. Farq yeh nahin ke kis model ko prompt kiya. Farq yeh nahin ke kaun si features use ki. Farq yeh nahin ke prompt-engineering tricks kaun si lagai. Farq cognitive hai: Person A ne AI kholne se pehle apni position banai; Person B ne pehle reasonable-sounding paragraph se position inherit kar li.
Yeh crash course isi gap ko band karta hai. Chhe disciplines, teen short parts, koi code nahin. Har discipline AI ke aik distinct failure mode ko handle karta hai jab AI ko unsupervised chhor diya jaye. Mil kar yeh AI ko oracle se partner banate hain: oracle mein aap poochte hain, woh jawab deta hai, aap maan lete hain; partner mode mein aap predict karte hain, woh jawab deta hai, aap compare karte hain, phir decide karte hain.
Prerequisite. Yeh page assume karta hai ke aap 2026 mein AI Prompting complete kar chuke hain. Us course ne mechanics sikhaye thay: context, reasoning modes, deep research, multimodal, AI desktop apps. Yeh course woh discipline sikhata hai jo mechanics ko payoff deta hai. Abhi dusre tab mein Claude, ChatGPT, ya Gemini ka free account khol lein. Practice callouts mein aap usay use karein ge.
Thesis aik line mein
Deliverable kabhi answer nahin hota. Deliverable thinking ka documented evidence hota hai.
Essentials: paanch bullets
Yeh paanch bullets is page ka map hain; page khud nahin. Inhein map ke taur par parhein; neeche ki disciplines territory hain. Bullets batate hain kya karna hai; neeche ki disciplines batati hain ke yeh kaam real work mein kaise karna hai, baghair 2023 wali purani prompting habits mein wapas jaaye.
- Prompt se pehle predict karein. Aik dafa aap AI ka answer parh lein to usay un-read nahin kar sakte. Pehla reasonable-sounding paragraph woh jagah le leta hai jahan aap ki apni position aani thi. Koi tool kholne se pehle diagnosis, ranked questions, predicted answers, aur confidence seal karein.
- Receipt hi deliverable hai. AI ke har decisive claim ke liye, jo ghalat ho to recommendation badal de, aap ACCEPT, REJECT, MODIFY, SURFACED, ya MISSED likhte hain, aur aik sentence ke kyun. Empty receipt ya all-ACCEPT receipt ka matlab hai real thinking nahin hui.
- Fluent prose accurate prose nahin hoti. AI sahi ho ya ghalat, confident lagti hai. Polished output ke andar chhe error types chhupi hoti hain. Forward, ship, ya act karne se pehle unhein naam se scan karein.
- First-order kabhi poora answer nahin hota. AI visible variable optimize karti hai aur woh teen variables ignore kar deti hai jinhein us ne abhi disturb kiya. Har meeting-worthy decision ka cascade map banayein. Kam az kam aik feedback loop dhoondhein. Labels nahin, mechanisms maangein.
- Collaboration teesra rasta hai. Solo speed mein haarta hai. AI-only originality mein haarti hai. Collaboration dono jeetti hai, lekin sirf jab deciding reasoning aap karein aur tedium AI kare. Yeh split ulat dein to aap question aur answer ke darmiyan middleman ban jate hain. Middlemen automate ho jate hain.
Chhatti discipline, First Principles, aur upar ke paanch bullets ke peeche ki practice scaffolding hi woh tareeqa hai jis se aap is list ko real work mein operationalize karte hain.
Figure 1: Chhe disciplines AI ke chhe failure modes se map hoti hain, teen arcs mein arranged. Detection ke liye Foundations chahiye; Origination ke liye dono.
Baad mein yeh disciplines obvious kyun lagti hain
Upar ke paanch bullets parh kar aam reaction aadha shrug hota hai: haan, bilkul. Prompt se pehle predict karein. Decisions document karein. Errors check karein. Second-order effects trace karein. Woh boundary dhoondhein jahan consensus toot ta hai. Accept karne ke bajaye collaborate karein. Yeh naye ideas nahin hain. Lindy Effect, yani yeh heuristic ke jo cheez lambe arsay se survive kar rahi hai woh aage bhi survive karne ka chance rakhti hai, exactly yahi kehta hai: cognition category ke old-looking ideas old is liye lagte hain kyun ke pehle ki har generation unhein test kar chuki hoti hai. Predict-before-you-prompt chaar so saal purana courtroom rule hai. Reasoning receipts woh tareeqa hai jis se editors drafts hamesha parhte aaye hain. Cascade maps second-year systems engineering hain. First principles Aristotle tak jate hain.
2026 mein disciplines nahin badleen. Unhein skip karne ki cost badal gayi hai. Jab polished output mehnga tha, bottleneck production tha: kya aap waqai cheez bana sakte hain? AI ne polished output free kar diya. Free account wala koi bhi twelve-year-old aisa memo bana sakta hai jo finished lagta hai. Bottleneck evaluation par shift ho gaya: kya aap bata sakte hain ke cheez sahi hai? Confidently wrong AI analysis no analysis se zyada dangerous hai, kyun ke woh finished lagti hai. Neeche ki disciplines ab optional achi habits nahin. Yeh woh jagah hain jahan aap ka judgment doosron ko visible hota hai, aur judgment hi woh cheez hai jo AI fake nahin kar sakti.
Lindy point ka doosra hissa: tools har chhe months badalte hain; thinking nahin. Jin teams ne apna poora 2023 workflow aik AI product ke gird banaya, unhein 2024 mein bhi rebuild karna para aur 2025 mein bhi, jaise hi model releases ne surface reshuffle ki. Products ke neeche wali skills apni value rakhti hain jab products nahin rakhte. Us par bet karein jo tikta hai.
Reading paths
Aaj aap ke paas jitna waqt hai, us hisaab se is page ko parhne ke teen tareeqe:
- 30-minute taste (first-time read, ya agar sirf coffee break hai): Disciplines 1, 2, 3, aur 6 parhein. Yeh chaar sab se important shifts cover karte hain: prompt se pehle predict karna, kaam ke dauran verdicts document karna, AI output ko chhe error types ke naam se scan karna, aur AI ko oracle samajhna band karna. Discipline 2 (Reasoning Receipt) short hai lekin decisive. Isay skip karein ge to Prediction Lock hoga magar room mein defend nahin kar sakein ge. Disciplines 4 aur 5 ke liye baad mein wapas aayein jab real work mein farq mehsoos ho.
- 90-minute essential read (standard path, recommended): Chhe disciplines order mein parhein. Har worked example parhein. Is week har discipline ka kam az kam aik practice callout chalayein. Optional Blank Page Sprint extension skip kar dein.
- Full read with practices (taqreeban do ghante plus aik hafta real-work application): Is page par sab kuch, plus har practice exercise apne agle saat dinon ke real decisions par chalayein. Yeh path instincts banata hai. Prediction Lock pehli dafa try karein ge to aap ke predicted answers vague ya ghalat hon ge. Yahi point hai. Aap ki prediction aur AI ke answer ka gap hi calibration ki jagah hai.
Woh path chunein jo aap ke week se match karta hai. Disciplines real problems par chalane se stick hoti hain, aik dafa parhne se nahin.
Part 1: Foundations (posture)
Do habits aage aane wali har cheez ki bunyaad hain. Agar aap har aur section skip karein, yeh do skip na karein. 2026 mein AI ka pehla failure mode yeh hai ke woh khushi se aap ki taraf se soch leti hai. Aap apni position banane se pehle woh finished-sounding answer de deti hai. Doosra failure mode: first draft bohat jaldi finished mehsoos hota hai. AI ki polish completeness jaisi lagti hai, is liye aap evaluate karne se pehle ship kar dete hain. Discipline 1 (Prediction Lock) woh posture hai jo aap AI kholne se pehle lete hain. Discipline 2 (Reasoning Receipt) woh artifact hai jo aap AI ke saath kaam karte waqt banate hain. Dono mil kar judgment human ke paas rakhte hain jab model heavy lifting karta hai. Parts 2 aur 3 mein sab kuch assume karta hai ke yeh dono jagah par hain.
Discipline 1: Prediction Lock
Aap AI se aik aisa sawal poochte hain jo matter karta hai. Answer fast aur smooth wapas aata hai. Aap sir hila dete hain. Aap usay forward kar dete hain, ya us par act kar lete hain. Do din baad koi poochta hai kyun aap us direction mein gaye, aur aap ko pata chalta hai ke jawab AI ka tha. Neeche aap ka apna jawab nahin tha.
Fix sticky note par chaar lines hai. Teen minutes. AI kholne se pehle. Samjhana mushkil, karna asan; is liye pehle kisi aur ke decision par saath chalte hain.
Maya 13 saal ki hai. Us ke school ne email ki: aik summer track choose karo. Debate camp (do haftay, sab dost ja rahe hain) ya coding bootcamp (aik hafta, curiosity hai magar thori nervous hai). Us ke dad us ke kandhe ke upar email parhte hain. "Bas ChatGPT se pooch lo, usay pata hoga."
Maya ki jagah khud ko rakhein. Question bhejne se pehle us ke liye chaar lines likhein.
Step 1. Aik sentence mein, yeh decision asal mein kis bare mein hai?
Agar aap ne likha "debate ya coding karni hai," dobara koshish karein. Yeh label hai, decision nahin. Decision woh hai jo label chhupa raha hai. Shayad yeh is bare mein hai ke woh doston ke saath jayegi ya woh choose karegi jo woh akeli hoti to karti. Ya kya coding miss karne ka regret debate miss karne se zyada hoga. Ya kya woh nervous hone ke bawajood curiosity follow karne ke liye ready hai. Jo closest lage, aik sentence mein likhein. Cause, topic nahin.
Step 2. Woh aik question jiska answer sab se bara hissa settle kare.
Maya ChatGPT se sab kuch nahin pooch sakti. Woh aik question kya hai jiska answer us ke liye decision narrow karega?
Agar aap ne general sawal likha ("which is better?"), dobara koshish karein. Question ko specific cheez par point karna chahiye: number, name, measurement, ya particular fact. "Kya bootcamp Python use karega?" specific hai. Us ka school already 9th grade mein Python padhata hai, is liye answer decision change karta hai. Maya ke liye apna aik question likhein.
Step 3. Answer ke bare mein aap ka guess.
Specific. "It depends" nahin. Agar question hai "kya bootcamp Python use karega?", aap ka guess yes ya no hai. Agar question hai "September mein us ke kitne dost ab bhi close hon ge?", aap ka guess number hai ("taqreeban aadhe").
Agar aap guess nahin kar sakte, question bohat vague tha. Usay narrow karein ya doosra choose karein. Apna guess likhein.
Step 4. Kitne sure hain, aur kya cheez Maya ka mind change karegi.
Us par percentage lagayein. 60%, 75%, number matter nahin karta. Number attach karna matter karta hai. Phir aik specific cheez name karein jo usay flip karegi. "70%. Agar bootcamp woh cheez use karta hai jo school already padhata hai, debate wins kyun ke debate usay kahin aur nahin milegi."
Agar aap flip-condition name nahin kar sakte, aap ke paas position nahin. Aap ke paas hope hai. Step 3 dobara likhein jab tak Step 4 mein kuch real na aa jaye.
Maya ki sticky ab yeh kehti hai:
Kya ho raha hai: Kya woh doston wali cheez karegi ya woh jo akeli hoti to choose karti. Question: Kya bootcamp Python use karega (jo us ka school already 9th grade mein padhata hai)? Guess: Yes. Kitni sure, kya flip karega: 70%. Agar bootcamp woh cheez use karta hai jo school nahin padhata, debate wins.
Ab woh apna aik question ChatGPT mein type karti hai. Yeh actual prompt hai jo woh paste karti hai:
My school's summer program runs a one-week coding bootcamp. I'm trying
to figure out one thing: will it teach Python? My school already teaches
Python in 9th grade, so I want to know if there's overlap. Just answer
the question. Don't recommend which camp I should pick.
Notice karein us ne "which should I pick" nahin poocha. Us ne apna specific Step 2 question poocha, aur aik line add ki ke AI us ke liye decision na kare. Yahi move hai.
ChatGPT jawab deta hai: "Most one-week coding bootcamps for middle schoolers cover Python basics in the first two to three days." Maya isay apni sticky ke saath compare karti hai. Us ka guess (yes) AI ke answer (yes) se match karta hai. Lock kaam aa gaya: bootcamp zyada tar wohi repeat karega jo usay 9th grade mein milna hai. Woh debate choose karti hai. Dinner par dad poochta hai kyun, aur us ke paas apni wajah ready hai, ChatGPT ka hedge nahin.
Yeh chaar lines Prediction Lock hain. AI ka confident answer aap ke dimagh mein aap ke apne answer ki jagah le, us se pehle teen minutes ki writing. Aik dafa AI ka answer us jagah par parh liya to aap usay un-read nahin kar sakte. Aap yeh bhi nahin bata sakte ke us ke baghair aap kya sochte. Bas do din baad notice hota hai ke aap explain nahin kar pa rahe ke aap ne jo decide kiya, kyun kiya. Aap ne AI ka answer absorb kiya. Apna answer earn nahin kiya.
Pehle apni prediction likhein, warna likhna hi chhor dein.
Same move higher stakes par bhi kaam karta hai. Aik bank manager, do losing branches close karne ka decision lete hue, apni chaar lines likhti hai: "Branches paisa is liye lose kar rahi hain kyun ke customers mobile par shift ho gaye. In branches ke deposits ka kitna fraction mobile-only customers ka hai? Guess: 70%+. 60% sure; 50% se neeche hua to closure case collapse." Phir us ne AI se apna aik question poocha. AI 45% ke saath wapas aaya. Us ka guess ghalat tha, lekin sawal sahi tha. Us ke number aur AI ke number ke darmiyan gap us memo ki opening line ban gaya jo woh boardroom mein le gayi.
Maya ki chaar lines aur bank manager ki chaar lines surface par different lagti hain. Move wohi hai.
Khud try karein
Submit karne ke liye zaroori nahin ke aap ka apna decision ho. Maya ke liye jo chaar lines aap ne abhi likhi hain woh real practice hain; agar kuch aur yaad nahin aa raha to wahi paste kar dein. Agar apni life mein kisi decision par yeh move chalana chahte hain, common examples yeh hain: $50 se upar koi purchase jis par aap soch rahe hain, do activities jin mein se sirf aik choose kar sakte hain, aik conversation jise aap avoid kar rahe hain, ya class/commitment jiske bare mein unsure hain.
Har surat mein: chaar lines likhein. Phir agar aap waqai AI se poochna chahte hain, yeh template hai (Maya wali shape):
I'm trying to decide [your situation in 1-2 sentences].
My specific question is: [your Step 2 question].
Just answer that one question. Don't make the decision for me.
AI ka answer pehle na dekhein. Neeche AI aap ki chaar lines ki FORM grade karta hai (kya "what's going on" cause name karta hai, label nahin; kya question options ko narrow karta hai; kya guess itna specific hai ke ghalat ho sake; kya flip-condition real way out deti hai), yeh nahin ke aap ka decision sahi hai ya nahin. Aap ki pehli attempt Maya ke liye likhi hui lines se messy hogi. Yeh assignment hai, failure mode nahin.
AI yeh check karega:
- Kya aap ka "what's going on" cause name karta hai, ya sirf label? 1-10 rate kare. Mere work ka woh hissa quote kare jo decision karta hai.
- Kya aap ka question, agar answer ho jaye, aap ke real options narrow karega? 1-10 rate kare. Aik aur cause name kare jo same situation fit karta ho lekin aap ka question meri cause se distinguish na karta ho.
Mera work rewrite na karein. Agar field empty ya vague ho, seedha keh dein. Messy first attempt ke bare mein honest rahen; na flatter karein, na crush karein.
Aap ka "what's going on" (cause, label nahin):
Aap ka aik question (jiska answer sab se bara hissa settle karega):
Aap ka guess (specific, hedge nahin):
Kitne sure, aur kya aap ko flip karega:
Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.
Pehli dafa 8 minutes plan karein. AI ke feedback ke saath sab se useful move: aik jagah dhoondhein jahan aap disagree karte hain. Aap ka judgment wahi rehta hai.
Half discipline. Doosri half (conversation ke dauran AI ke kaun se claims accept, reject, ya modify karte hain, usay log karna) Discipline 2 hai.
Yeh kyun kaam karta hai (short version)
Outside source consult karne se pehle apna guess likhna AI se decades purana hai. Gary Klein ne workplace version ko "project premortem" kaha (Harvard Business Review, 2007): imagine karein project fail ho chuka hai, aur start se pehle reasons likhein. Same idea. Phil Tetlock ki forecasting research (Good Judgment Project, Superforecasting, 2015) ne dikhaya ke calibration tab improve hoti hai jab aap answer aane se pehle prediction record karte hain, baad mein nahin. Aur Tversky aur Kahneman ke anchoring work (1974) ne dikhaya ke aik confident answer jab us jagah occupy kar leta hai jahan aap ka apna answer aana tha, to aap bata nahin sakte ke us ke baghair aap kya sochte.
Prediction Lock in teeno ka AI version hai.
Is exercise ka full version (10 ranked questions plus Reasoning Receipt template; 45-60 minutes) Part 0 Chapter 1, Lesson 1 mein hai. Yeh page move sikhata hai. Woh page isay system banata hai.
Discipline 2: Reasoning Receipt
Aap ne subah Claude ke saath aik real document par iterate karte hue guzari. Output clean hai. Aap ne slides mein drop kiya, meeting chalai, move on kar gaye. Do haftay baad post-mortem mein boss poochta hai: "Kis parts par tum ne waqai push back kiya tha?" aur aap ko realise hota hai ke yaad nahin. Aap ne skim kiya, accept kiya, ship kiya. Deliverable pass ho gaya. Thinking nahin.
Fix yeh hai. AI ke saath kaam karte waqt har decisive claim ko paanch verdicts mein se aik ke saath log karein. Claim decisive hai agar woh ghalat ho to aap ki recommendation badal jaye.
| Verdict | Meaning | One-sentence why |
|---|---|---|
| ACCEPT | Aap ne claim as-is le liya. | Aap ne us par trust kyun kiya (source, prior experience). |
| REJECT | Aap ne claim discard kiya. | Kaun se evidence ne isay beat kiya. |
| MODIFY | Aap ne changed version use kiya. | Kya change kiya aur kyun. |
| SURFACED | AI ne woh point uthaya jo aap ne consider nahin kiya tha. Aap ne usay rakha. | Yeh kyun matter karta hai. |
| MISSED | Aap ne woh point uthaya jo AI ne catch nahin kiya. Aap ne add kiya. | AI ne kya miss kiya aur kyun matter karta hai. |
Is log ko Reasoning Receipt kehte hain. Real document mein receipt conversation ke saath row-by-row grow karti hai. Neeche exercise mein aap paanch claims aik saath receipt karein ge.
Receipt mein har row aik decision hai. Verdict batata hai aap ne kya kiya. Why batata hai future reader, including future you, is par trust kyun kare.
Real life mein yeh kaisa dikhta hai.
Aik product lead ne Claude se new feature ka launch plan draft karwaya. Claude ne clean three-page plan diya. Doc mein drop karne ke bajaye product lead ne side-by-side open kiya aur har claim par receipt banai jo ghalat hota to plan badalta:
| AI ka claim | Verdict | Why |
|---|---|---|
| "Launch ko single primary CTA ke saath ship karein taake conversion maximize ho." | ACCEPT | Hamari last three launches se match karta hai; one-CTA tests har dafa two-CTA tests ko beat karte hain. |
| "10% rollout cohort se start karein jisme paid users shamil hon." | REJECT | Paid users hamari least churn-tolerant cohort hain; rollout buggy hua to trust burn karte hain. |
| "Launch announcement Tuesday morning bhejein." | MODIFY | Tuesday yes; morning no. Is segment ke liye engagement window Tuesday 6-8pm hai. |
| "Feature ka overlap [competitor] ki March release se hai; differentiation se lead karein." | SURFACED | Competitor ki release timing compare nahin ki thi. Differentiation framing wins. |
| (AI ne new feature ke paid-tier pricing implications mention nahin kiye.) | MISSED | Maine note add kiya: launch se pehle pricing review hona chahiye warna legacy ko discounts hand ho jayein ge. |
Us ne launch plan ke saath receipt bheji. Do haftay baad CEO ne poocha ke rollout mein paid cohort kyun skip ki. Us ne row 2 dikhai. Conversation ninety seconds mein khatam hui. Receipt ke baghair yeh thirty-minute defend-yourself meeting hoti jahan woh reconstruct nahin kar pati ke actually kya decide kiya tha.
Receipt ke baghair wohi product lead yeh produce karti:
| AI ka claim | Verdict | Why |
|---|---|---|
| "Launch ko single primary CTA ke saath ship karein." | ACCEPT | Sahi lagta hai. |
| "10% rollout cohort mein paid users shamil karein." | ACCEPT | Sahi lagta hai. |
| "Tuesday morning launch announcement bhejein." | ACCEPT | Sahi lagta hai. |
| "[competitor] ke against differentiation se lead karein." | ACCEPT | Sahi lagta hai. |
| (Kuch logged nahin.) |
Paanch ACCEPTs aik row mein do cheezon mein se aik ka matlab rakhte hain: ya AI har cheez par right hai (rare), ya receipt real kaam nahin kar rahi. All-ACCEPT receipt no receipt ke barabar hai. Har "why" likhne ki friction hi discipline hai. Agar aap real "why" nahin likh sakte to aap ne claim actually accept nahin kiya. Aap ne inherit kiya.
Khud try karein
Aap 60-person B2B SaaS company mein product head hain (mid-market sales teams ke liye CRM tooling, ~$12M ARR, 30% year over year growth). Feature redesigned reporting layer hai jo top customers chhe months se maang rahe hain. Current version mein do non-critical edge-case bugs known hain jo roughly 4% accounts affect karte hain. Closest competitor ne similar feature last week launch kiya. Aap ne AI se poocha: "Should we ship this feature now, or wait two weeks for more testing?" AI ne five-claim recommendation di. Har claim ko paanch verdicts mein se aik aur one-sentence why ke saath receipt karein.
- "Ship now. Speed-to-market early adoption mein dominant variable hai."
- "Two-week delay se news cycle lose hone ka risk hai, kyun ke [competitor] ne last week apna version launch kiya."
- "Aap ki last three launches ki production telemetry dikhati hai ke defects week 1-3 mein surface hote hain, is liye two extra weeks of testing unhein catch nahin karein ge."
- "Customer support load launch ke first week mein aam tor par 40% rise karta hai."
- "Defended ship ke dauran engineering velocity 15% drop hoti hai."
(Agar aap software ship nahin karte, surface swap karein: AI ne aap ke week ke real decision par five-claim recommendation di hai. Usay use karein.)
Form se pehle aik note. Neeche feedback frontier model ke liye tuned hai (Claude Sonnet 4.5+, Opus 4.7, GPT-5, Gemini 2.5 Pro). Smaller models input quality se qata nazar handwave karte hain.
AI yeh check karega:
- Kya aap ne har verdict ke liye real "why" likha, ya "sounds right" / "makes sense" patterns? 1-10 rate karega. Meri receipt ka weakest "why" quote karega.
- Kya kam az kam aik REJECT ya MODIFY, plus kam az kam aik SURFACED ya MISSED hai? Agar har verdict ACCEPT hai to receipt kaam nahin kar rahi. 1-10 rate karega. Agar meri receipt all-ACCEPT hai to aik line mein seedha kahega.
Mera work rewrite na karein. Personality par grade na karein. Agar field empty ya vague ho to seedha kahe.
Claim 1 ke liye ("Ship now. Speed-to-market dominant variable hai"):
Claim 2 ke liye ("Two-week delay se news cycle lose hone ka risk hai"):
Claim 3 ke liye ("Production telemetry dikhati hai defects week 1-3 mein surface hote hain"):
Claim 4 ke liye ("Customer support load aam tor par 40% rise karta hai"):
Claim 5 ke liye ("Engineering velocity defended ship ke dauran 15% drop hoti hai") YA apni MISSED row:
Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.
Pehli dafa 10-15 minutes rakhein. Baad mein fast ho jata hai. AI feedback ke saath sab se useful kaam yeh hai ke aik row dhoondhein jahan aap ne "sounds right" likha baghair earn kiye. Woh row hai jahan aap kisi aur ki reasoning apne naam se ship karne wale thay. Us row ko real "why" ke saath dobara receipt karein aur exercise ki cost wapas aa chuki.
Aap ne abhi decisive claims ko aik aik kar ke catch kiya. Yeh har claim ke andar chhupi technical errors nahin pakarta: fabricated citations, stale facts, false confidence. Woh scan Discipline 3 hai.
Compare karne ke liye strong sample chahiye? (Apna submit karne ke baad kholein.)
Isi ship-now-or-wait scenario par aik reader ne yeh likha. Yeh akela good answer nahin; shape dikhata hai.
| Claim | Verdict | Why |
|---|---|---|
| 1 | REJECT | Speed-to-market commodity markets mein dominate karta hai, hamare mein nahin: hum compliance-bound buyers ko sell karte hain jo bugs ko slowness se zyada punish karte hain. |
| 2 | MODIFY | Competitor ne related feature launch ki, hamari nahin: differentiation news cycle se zyada matter karti hai, aur cycle already over hai. |
| 3 | ACCEPT | Hamari last three launches se match karta hai: hotfixes weeks 1-3 mein hote hain, weeks 4-6 mein almost never. |
| 4 | SURFACED | Maine support lift 20% budget ki thi, 40% nahin: support team ke paas 1.5 weeks headcount cushion hai, jo mere liye real risk close karta hai. |
| 5 | MISSED | AI ne yeh nahin uthaya ke two more weeks humein hamare biggest customer ke annual planning lock-in window mein dhakel dete hain; yahi real limit hai. |
Isay kaamyaab kya banata hai: sirf aik ACCEPT, woh bhi real evidence ke saath. Paanch mein se do Whys prior internal data quote karte hain, vibes nahin. MISSED row woh constraint catch karti hai jo AI nahin jaan sakti thi (customer planning calendar). Reader ka decision "wait, because of customer lock-in" banta hai, jo "wait, because more testing" se different answer hai. Same verdict, different reasoning, room mein defensible.
Yeh kya karne ki koshish nahin karta: brilliant banna. Zyada tar rows aik sentence hain. Discipline real Whys likhne mein hai, literary Whys nahin.
Is move ke neeche cognitive science dekhni ho to kholein
Receipt AI se bohat purani cheez hai.
- Schon, D. (1983). The Reflective Practitioner. Direct ancestor. Schon ki "reflection-in-action" ka move hai kaam hote waqt decisions ka written track banana taake practitioner baad mein har decision defend kar sake. Reasoning receipt model ke saath kaam par reflection-in-action hai.
- Argyris, C. (1977). "Double Loop Learning in Organizations." Harvard Business Review. Single-loop learning existing model ke against errors correct karti hai; double-loop learning model khud surface karti hai. All-ACCEPT receipt single-loop at best hai. Har Why likhne ki friction second loop force karti hai.
- Brown, P. C., Roediger, H. L. & McDaniel, M. A. (2014). Make It Stick. Retrieval practice aur elaboration research ka popular synthesis. Apne words mein aik sentence likhna ke cheez kyun matter karti hai, months later memory ko improve karta hai. Receipt aap ke apne decisions par retrieval practice hai; boss-asks-six-months-later moment exactly wahi scenario hai.
Reasoning Receipt ko AI specifically ke liye test karne wali single trial nahin. Mechanism (decisions likhein jab ban rahe hon, baad mein defend karein) well-studied hai; AI interactions par apply karna obvious extension hai.
Go deeper: Part 0 Chapter 1: Asking Better Questions. Full version (real AI conversation ke against 10-row receipt plus Contradiction Challenge, 45-60 min) foundational sequence ka hissa hai. Yeh page move sikhata hai. Woh chapter har high-stakes AI conversation par habit banata hai.
Part 2: Detection (jo AI miss karti hai usay catch karna)
Foundations ne posture diya. Detection woh pattern recognition train karti hai jo AI ki consistent misses catch karti hai. Do failure modes yahan dominate karte hain. AI sahi ho ya ghalat, confident lagti hai, aur us ki zyada tar errors un paragraphs mein chhupi hoti hain jo sab se professional parhte hain. AI visible variable optimize karti hai aur un teen variables ko ignore karti hai jinhein abhi disturb kiya. Discipline 3 (Error Taxonomy) named-category scan hai jo aap fluent prose ke against chalate hain taake chhe specific error types ship hone se pehle mil jayein. Discipline 4 (Thinking in Systems) cascade map hai jo aap har meeting-worthy decision ke against draw karte hain taake second-order effects milen jo AI ne trace nahin kiye.
Discipline 3: Error Taxonomy
Aap trap jaante hain. Aap real document Claude ya ChatGPT mein paste karte hain, answer polished aur fluent wapas aata hai, aur aap usay apni writing ki tarah parhte hain: general sense ke liye, argument ki shape dekhte hue. It flows. Aap nod karte hain. Error draft ke sab se professional paragraph mein baithi hoti hai, woh jis par aankh is liye skip kar gayi kyun ke kuch wrong mehsoos nahin hua. Teen din baad woh ship hota hai, aur aik fabricated number ya nonexistent citation pehli cheez ban jati hai jo reader catch karta hai.
Fix yeh hai. AI output ko "feel" se na parhein; har error type ko naam se scan karein. Chhe types, har aik ke saath where-to-look-first prompt.
| Error type | Kaisa dikhta hai | Pehle kahan dekhein |
|---|---|---|
| Factual error | Demonstrably false specific claim: number, date, name, citation, API method. | Har sentence jisme specific number ho, khaas tor par decimals. Precision research ka appearance banati hai. Main keh sakta hoon ke 73.6% analysts AI figures verify nahin karte, aur yeh credible lagega. Maine yeh das seconds pehle bana diya. |
| Logical gap | Conclusion stated premises se actually follow nahin karta. | "Evidence" aur "therefore" ke bridge par. "Therefore" bracket karein aur poochein: kya yeh follow karta hai, ya missing link main khud supply kar raha hoon? |
| False confidence | Uncertain information certain tone mein stated ho. | Sab se fluent paragraphs. Hedging language ("may," "could") signal hai ke AI jaanti hai yeh thin ice hai; contested topic par us ki absence red flag hai. |
| Missing context | Crucial factor omit ho gaya jo analysis badal de. | Woh jo subject-matter expert pehle poochega. Agar aap poochein "wait, did you consider X?", AI ne shayad nahin kiya. |
| Fabricated source | Citation, library function, ya API jo exist nahin karta, ya exist karta hai lekin AI wali baat nahin kehta. | Har citation, quoted statistic, external function call. Forward ya run karne se pehle verify karein. |
| Stale fact | Kabhi true tha, ab true nahin. | Time-sensitive cheezen: prices, leadership, laws, API versions, tool ki capabilities. |
Real documents par har category ko naam se scan karein. Neeche exercise mein do named scans karte hain (Factual aur Fabricated Source se start) taake move feel ho; full six-row pass worked example mein hai.
Chhe error types apna announcement nahin karti. Woh un paragraphs mein chhupi hoti hain jo sab se professional parhte hain, isi liye naam se scan karna feel se parhne se behtar hai.
Real life mein yeh kaisa dikhta hai.
Aik buy-side equity analyst mid-cap industrial name mein $25M position ke liye recommendation memo bana rahi thi. Investment Committee ninety minutes mein milne wali thi. Us ne Claude se four-paragraph thesis section draft karwaya, company ke last two 10-Qs, latest analyst-day transcript, aur apni notes feed ki. Claude ne clean draft diya: revenue growth, multiple expansion, bank-analyst quote, Q3 cash-flow figure, thesis paragraph. Us ne paste nahin kiya. Us ne six-row scan chalaya.
| Error type | Draft mein kya mila | Verdict |
|---|---|---|
| Factual error | Draft ne kaha: "Q3 operating cash flow of $182M, up 14% year-over-year." Us ki 10-Q tab ne $164M, up 9% dikhaya. 11% off. | Caught. Primary source se corrected. |
| Logical gap | Draft ne kaha: "Comparable peers trade at 14x forward EBITDA; therefore the name is undervalued at 11x." "Therefore" ne assumption smuggle ki ke peer set actually comparable hai. Teen peers mein se do ke margins higher thay. | Caught. Margin-adjusted multiple ke saath rewrote. |
| False confidence | Draft ne kaha: "Management's $2.3B revenue guidance for next year is conservative." No hedge. No basis. "Conservative" sara kaam kar raha tha. | Caught. "Above consensus by 4%" ke taur par rewrote. |
| Missing context | Draft ne mention nahin kiya ke company's largest customer (22% revenue) active RFP mein tha jo IC ke next quarterly review se pehle close hota. Us ki sector notes mein tha; Claude ke paas woh note nahin tha. | Caught. First risk bullet add kiya. |
| Fabricated source | Draft ne cite kiya: "As Morgan Stanley's industrials desk noted in their November initiation, the multiple compression is overdone." Us ne FactSet search kiya. Aisa note exist nahin karta tha. Claude ne do real reports ko confident fiction mein blend kiya. | Caught. Quote remove ki; citation ke baghair rewrote. |
| Stale fact | Is draft mein time-sensitive kuch slip nahin hua. Pricing data, leadership, rules current thay. | Actively scanned. Clean. |
Single four-paragraph draft mein six categories mein se five trigger hui, aur fabricated bank quote woh thi jo woh almost miss kar deti kyun ke woh exactly Morgan Stanley desk jaisi lagti thi. IC deck mein gaya version line by line re-evidenced tha. IC ne position approve ki. Baghair scan ke version real bank se attributed fake quote ke saath us ke naam se memo mein jata.
Naam se scan kiye baghair wohi person yeh ship karti:
| Reader habit | Kya miss hota hai | Kyun fail hota hai |
|---|---|---|
| Top-to-bottom parhna ke "argument hold up karta hai?" | Specific numbers. Eye fluent paragraph ke andar figures skim karti hai. | $182M cash-flow figure woh detail hai jise nod kar ke skip kar dete hain. "Factual" ko naam se scan karna har number par stop force karta hai. |
| Citations par trust kyun ke credible lagti hain | Morgan Stanley quote. Real bank, plausible thesis, fabricated note. | "Looks credible" failure mode khud hai. "Fabricated Source" ko naam se scan karna har citation par verification force karta hai. |
| "Therefore" ko connector word parhna | Peer-comparable logical gap. "Therefore" hide karta hai ke bridge actually hold karta hai ya nahin. | Argument shape parhna connector words ko unchecked load-bearing kaam karne deta hai. Har "therefore" bracket karna bridge ko defend karne par majboor karta hai. |
| Missing cheezen sirf tab notice karna jab jump out karein | Active RFP mein 22% customer. Draft mein nahin, is liye visual catch nahin. | Missing context page par flag nahin uthata. Actively poochna parta hai ke next desk ka analyst kya notice karega jo model nahin kar saka. |
Same person, same draft, same hour. Farq smarts nahin. Farq yeh hai ke aap ne naam se scan kiya ya feel se.
Khud try karein
Aap investment analyst hain. Aap ne AI se NorthBridge Industrial Holdings (NBIH), aik mid-cap industrial supplier, mein $25M position ke liye recommendation memo draft karwaya. Investment Committee 90 minutes mein milti hai. Yeh AI ka four-paragraph draft hai. Isay six error types ke naam se scan karein, Factual aur Fabricated Source se start karte hue, aur neeche grid fill karein.
Investment Memo: NorthBridge Industrial Holdings (NBIH), DRAFT
NorthBridge Industrial Holdings FY2024 revenue of approximately $1.8B ke saath mid-cap industrial supplier hai. Q2 2026 operating cash flow $214M aaya, 17% year-over-year up, double-digit cash-flow growth ki fourth consecutive quarter. Gross margin 38.4% NBIH ko sector ke top quartile mein rakhta hai. Management's $2.1B revenue guidance for FY2026 reported backlog ki strength dekhte hue conservative posture reflect karti hai.
Comparable peers industrial-supplier set mein approximately 13.5x forward EBITDA par trade karte hain; NBIH currently 10.2x par trade karta hai. Therefore name roughly 25% undervalued hai, jo next two quarters mein kisi earnings beat par meaningful re-rating potential suggest karta hai. Mean-reversion thesis company's recent capital-return announcement aur broader sector rotation into industrials over the past six weeks se supported hai.
Goldman Sachs ne apne April 2026 industrial-supplier sector primer mein note kiya: "industrial suppliers with backlog visibility above 9 months are the most reliable beneficiaries of capex normalization." NBIH ka reported backlog 11.2 months hai. Pichle 90 days mein insider buying $4.2M across three executives total hai, three years mein NBIH ki highest insider-buying activity. Technical setup constructive hai: 50-day moving average mid-March mein 200-day se upar cross hui.
Recommendation: BUY, 12-month price target $84 (current price $68), implying 23.5% upside. $25M position size fund AUM ka 2.1% hai, fund ke high-conviction sizing framework se consistent. Principal risk general industrial cyclicality hai; NBIH otherwise well-positioned hai.
(Agar buy-side analysis aap ka work nahin, surface swap karein lekin shape rakhein: AI-drafted document kisi senior decision-maker ko ja raha hai, fluent prose, named claims jo verify ho sakte hain, aur itna time nahin ke teen dafa parhein. Grant report, clinical summary, board memo, vendor risk note. Taxonomy domain se indifferent hai.)
Form se pehle aik note. Neeche feedback frontier model ke liye tuned hai (Claude Sonnet 4.5+, Opus 4.7, GPT-5, Gemini 2.5 Pro). Smaller models aap ke pasted scan ko confirm karte hain, jo exercise ko defeat karta hai.
AI yeh check karega:
- Kya aap ne naam se scan kiya, ya feel se parh kar baad mein label lagaya? 1-10 rate karega. Meri grid ki woh row quote karega jis se decision hota hai. Real named scan har row ke liye verdict deta hai, even "actively scanned, found nothing." Baghair is note ke blank row tell hai.
- Kya aap ki quoted sentences recommendation badal sakti hain agar wrong hon, ya aap ne easy lines flag ki? 1-10 rate karega. Jis row mein sentence quote ki ho, same draft se aik stronger candidate name karega agar meri AI draft mein ho.
Mera work rewrite na karein. Writing style par grade na karein. Agar row empty hai aur "actively scanned, none found" note nahin hai to aik line mein seedha kahe.
Aap ki 6-row scan grid (har row mein exact AI sentence quote karein; row blank sirf tab chhorein jab actively scan kar ke kuch na mila ho, aur us row mein "actively scanned, none found" likhein):
Har row par aap ka confidence (1-10 per error type; aik sentence ke kyun):
Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.
Pehli dafa 8-15 minutes rakhein. Baad mein fast ho jata hai. AI feedback ke saath sab se useful kaam yeh hai ke aik jagah dhoondhein jahan AI aap ke scan se disagree karta hai. Woh disagreement next round ka judgment banata hai.
Aap ne abhi output ki local errors catch ki. Yeh un second-order effects ko catch nahin karta jo aap ka output downstream trigger karega: recommendation land hone par morale hit, policy ship hone par customer behavior change, woh loop jahan cost savings service quality gira kar churn barhati hain. Yeh Cascade Map hai, Discipline 4.
Compare karne ke liye strong sample chahiye? (Apna submit karne ke baad kholein.)
Investment-memo scenario par aik reader ne yeh grid banai. Yeh akela good answer nahin; shape dikhata hai.
| Error type | AI draft se quoted sentence | Kyun trigger hota hai |
|---|---|---|
| Factual error | "Q3 operating cash flow of $182M, up 14% year-over-year." | Specific number, 10-Q ke against verifiable. 10-Q $164M, up 9% kehta hai. Level aur growth rate dono wrong. |
| Logical gap | "Comparable peers trade at 14x forward EBITDA; therefore the name is undervalued at 11x." | "Therefore" assume karta hai ke peer set comparable hai, jo argue nahin hua. Three peers mein se two structurally higher margins rakhte hain. |
| False confidence | "Management's $2.3B revenue guidance for next year is conservative." | No hedge. No basis. "Conservative" directional claim ko fact bana kar present karta hai. |
| Missing context | (Draft se missing.) Company's largest customer, ~22% revenue, active RFP mein hai jo IC ke next review se pehle close hota hai. | Page par missing hona hi row ka point hai. Aap scan karte hain ke kya nahin hai. |
| Fabricated source | "As Morgan Stanley's industrials desk noted in their November initiation, the multiple compression is overdone." | Real bank, plausible quote, lekin aisa note exist nahin. FactSet ya bank publication tracker se verify hota. |
| Stale fact | Actively scanned, none found. Pricing, leadership, aur capital-allocation policy draft date tak current thay. | Is note ke baghair blank row skip hoti, finding nahin. |
Isay kaamyaab kya banata hai: har row verdict rakhti hai, even clean one. Quoted sentences IC ki read badal sakti hain; throwaway nahin. Missing Context row specific hai. Fabricated Source row exact sentence quote karti hai aur falsify karne ka tareeqa batati hai.
Yeh kya karne ki koshish nahin karta: exhaustive hona. Taxonomy scan hai, audit nahin. Fifteen minutes mein six rows target hai. Teen real catches tees performative catches se behtar hain.
Is move ke neeche cognitive science dekhni ho to kholein
Taxonomy older work ka 2026 application hai ke confident prose scrutiny ko kyun disarm karti hai.
- Alter, A. L. & Oppenheimer, D. M. (2009). "Uniting the tribes of fluency to form a metacognitive nation." Personality and Social Psychology Review 13(3), 219-235. Processing fluency ka canonical review: fluent, easy-to-process information ko actual accuracy se independent zyada credible judge kiya jata hai. Polished AI prose is effect ka modern industrial-scale version hai. Named-category scan ease-equals-truth shortcut interrupt karta hai.
- Silver, N. (2012). The Signal and the Noise. Penguin Press. Central argument: confidence aur calibration independent traits hain. Sab se certain forecasters aksar least calibrated hote hain. Taxonomy ki False Confidence row isi thesis ko AI output par operationalize karti hai.
- Gigerenzer, G. (2002). Calculated Risks. Simon & Schuster. Calibration work subjective confidence aur observed accuracy ke gap ko formalize karti hai. AI ke liye equivalent yeh scan hai: draft ko whole accept karne ke bajaye har category par verdict commit karna.
Named taxonomy AI-error detection ko specifically kitna improve karti hai, is par single trial nahin. Cognitive pattern well-studied hai; AI output par application obvious extension hai.
Go deeper: Part 0 Chapter 2: Detecting Broken Reasoning. Full version (8-category taxonomy, dual-AI cross-check, prediction-vs-actual calibration; 60-75 min) isay system banata hai.
Discipline 4: Thinking in Systems
Aik paragraph mein: jab aap decision ke bare mein poochte hain to zyada tar AI tools effects ki list dete hain. Jo woh miss karte hain woh feedback loops hain, jahan effects wapas circle kar ke original decision ko amplify ya undo karte hain. Cascade Map consequences ko multiple stakeholder groups ke across trace karta hai aur clean answer ship karne se pehle kam az kam aik loop ka naam likhwata hai.
Aap trap jaante hain. Aap ne AI se staffing change analyze karwaya, answer clean aaya, teen bullet points aur crisp recommendation. Aap ne usi afternoon ship kar diya.
Teen months baad next-door team ka morale collapse ho gaya, do clients aap ke group ke around route karne lage, manager jo quietly displaced work utha raha tha burn out ho gaya, aur leadership ne poocha kya hua to aap explain nahin kar sake. First-order answer correct tha. Second-order effects ne usay kha liya. Third-order effects abhi bhi room mein hain.
Fix yeh hai. Meeting-worthy decision par AI kholne se pehle paanch lines draw karein.
- Decision center mein. Aik sentence, no hedging. "Consider raising prices" nahin balkay "next quarter se new contracts par list prices 18% raise karein."
- Paanch domains spokes ki tarah bahar. Employees, customers, competitors, regulators, internal knowledge. Har domain aik branch.
- Har domain par teen "and then what?" layers. First-order effect. Phir us effect ka consequence. Phir us consequence ka consequence.
- Kam az kam aik feedback loop ka naam lein. Jahan downstream effect wapas circle kar ke original decision badalta hai. Mechanism state karein, label nahin. "Customers churn" nahin balkay "customers churn kyun ke new automated tier human ko ten seconds mein escalate nahin kar sakta, jab ke previous vendor karta tha."
- Sirf tab finish karein jab map messy lage. Agar neat hai to aap jaldi ruk gaye. Most strategic disasters woh loops hain jo kisi ne map nahin kiye.
Is drawing ko Cascade Map kehte hain. Point future predict karna nahin. Point clean answer ship karne se inkar karna hai.
AI us variable ko optimize karti hai jo aap ne poocha; woh un teen variables ke bare mein reason nahin karti jinhein woh disturb karti hai. Humans breadth miss karte hain (second domain, stakeholder jiska naam nahin liya). AI loops miss karti hai (feedback jo chhe months baad wapas aa kar gain unwind karta hai). Blind spots complementary hain. Is liye pehle map draw karein, phir AI ko branches stress-test karne laayen.
Real meeting-worthy decision par map 20-30 minutes le sakta hai. Neeche exercise smaller scope use karti hai taake muscle feel ho.
Paanch domains, consequence ki teen layers, aik named feedback loop. Mess feature hai, bug nahin.
Real life mein yeh kaisa dikhta hai.
Aik city planner ke paas 2.3-mile downtown commercial corridor par protected bike lanes add karne ki recommendation ke liye six-week window thi. First-order case clean tha: bike infrastructure mode shift, lower emissions, fewer cyclist injuries se correlate karti hai. Corridor ki cyclist-injury rate city average se 2x thi. Advocacy coalition organized aur patient thi. AI ne cheerfully case validate kar diya.
Memo forward karne se pehle us ne cascade map draw kiya. Central decision: protected bike lanes install karein; har direction se aik vehicle lane remove karein; curbside parking ka 40% remove karein. Paanch domains mein teen layers. Zyada tar second-order effects predictable thay (cyclists happy, drivers grumpy, kuch parking displacement). Third layer ne recommendation break open kar di.
Named loop ne memo badla: corridor businesses weekend visitor revenue lose karte hain, local tax base shrink hota hai, council pressure feed hota hai, next session mein policy weak hoti hai, original mode-shift gain erode hota hai, aur across town next corridor ka case mar jata hai. Is corridor ko karne ki poori reason next ten ke liye case jeetna thi.
Us ne project kill nahin kiya. Us ne 12-month loading-zone pilot, guaranteed bus-stop redesign budget, quarterly revenue threshold (>15% sustained drop triggers a revisit), aur transit-agency MOU on bus-stop access add kiya. Woh version council 7-2 survive kar gaya. Clean AI version mein yeh provisions nahin thay, aur dusri city mein colleague ki similar recommendation (no cascade, no provisions) fourteen months ke andar repeal ho gayi.
| Domain | 1st-order | 2nd-order | 3rd-order |
|---|---|---|---|
| Employees | Public-works curbs repaint karta hai | Parking enforcement budget loading conflicts cover karne ke liye rise hota hai | Transit drivers grieve karte hain jab buses relocated stops par cleanly pull nahin kar sakti |
| Customers | Cyclists protected route gain karte hain | Delivery drivers bike lane mein double-park karte hain | Corridor businesses weekend revenue dip dekhte hain; 3 relocation threaten karte hain |
| Competitors | Adjacent corridor car-friendly rehta hai | Woh corridor threatened businesses ko court karta hai | Tax base 18 months mein neighborhoods shift karta hai |
| Regulators | State DOT grant terms apply hote hain | ADA review bus-stop curb cuts flag karta hai | Compliance retrofit timeline 6 months push karta hai aur cost add karta hai |
| Internal knowledge | Old mode-shift study (3 yrs) | Assumptions stale; weekend traffic pattern shift hua | Planning dept forecast defend nahin kar sakta without refresh |
Named loop: corridor revenue loss -> tax-base reduction -> council pressure -> next session mein policy weakened -> mode-shift gains erode -> defenders next corridor ka case lose karte hain. Isi loop ne recommendation ko teeth diye.
Cascade ke baghair wohi person kuch aisa likhti:
| Domain | 1st-order | Kyun fail hota hai |
|---|---|---|
| Cyclists | Safer rides | Aik domain, aik layer. No loop. Delivery-driver double-parking dynamic entirely miss. |
| Emissions | Lower CO2 per mile | Metric hai, stakeholder nahin. Corridor-business revenue loop aur council feedback miss. Mechanism named nahin, sirf outcome asserted. |
Same person, same hour. Farq smarts nahin. Farq yeh hai ke aap ne messy map kiya ya clean ship kiya.
Khud try karein
Aap 200-person B2B SaaS company ke head of revenue hain (~$32M ARR; HR-tech vertical; 280 customers, top 20 revenue ka 55%; 18-month average contract length; 11-week average sales cycle; last quarter net revenue retention 108%). Next quarter leadership all new contracts par list prices 18% raise karna chahti hai aur standard discount ladder ko 0-to-30% range se 0-to-15% tak short karna chahti hai. Aap decision-recommender hain. Thursday exec read-out se pehle is pricing change ko cascade karein. Paanch domains directly apply karte hain: account executives (quota-attainment 74%), next 6 months mein renewal ke liye existing customers, do named competitors (aik slightly cheaper, aik slightly more expensive with stronger reporting), top accounts ki procurement teams (zyada tar annually formal RFPs chalati hain), aur aap ka sales-enablement collateral.
(Agar pricing aap ka work nahin, surface swap karein lekin shape rakhein: leadership decision jo kai groups ko aik saath affect karta hai, real deadline, aur kam az kam aik jagah jahan second-order effects first-order outcome ko feed back karte hain. Ya apne week ka real decision lein. Yahi isay stick karata hai.)
Form se pehle aik note. Neeche feedback frontier model ke liye tuned hai (Claude Sonnet 4.5+, Opus 4.7, GPT-5, Gemini 2.5 Pro). Smaller models input quality se qata nazar handwave karte hain.
AI yeh check karega:
- Kya aap ka map five domains wide aur three layers deep gaya, har link par mechanism ke saath label nahin? 1-10 rate karega. Thinnest domain ka naam dega aur aik specific effect jo aap miss kar gaye.
- Kya aap ka feedback loop real loop hai, mechanism causal sentence ke roop mein stated hai? 1-10 rate karega. Agar loop sirf label hai ("regulators react"), flag karega aur aik additional loop propose karega, mechanism likh kar.
Mera map redraw na karein. Style par rate na karein. Agar field empty ya vague ho to aik line mein seedha kahe.
Aap ka cascade map (central decision, phir 5 domains x 3 layers; rough text fine hai, structure visible rakhein):
Aap ka feedback loop, aik causal sentence ke taur par (label nahin):
Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.
Pehli dafa 15-20 minutes rakhein. Cascade maps Prediction Lock se longer run karte hain kyun ke value messy middle layers mein hai, aur first three ya four "and then what?" questions forced feel hotay hain before real ones surface. Fourth ya fifth usually woh third-order effect nikalta hai jo actually matter karta hai. Muscle ban jaye to faster; experienced cascaders full map eight to twelve minutes mein run kar lete hain.
AI feedback ke saath sab se useful kaam yeh hai ke aik domain dhoondhein jo AI ne add kiya aur aap ne miss kiya. Blind spot wahi rehta hai. Agar AI ne loop add kiya jo aap ne miss kiya, usay separate find mark karein. Loops move-the-needle hote hain kyun ke woh batate hain announced decision (18% list price increase) duniya mein kuch aur (4-6% realized) ban kar kaise aayega.
Aap ne abhi existing plan ke second- aur third-order effects stress-test kiye. Yeh nahin poochta ke plan shuru hi right assumptions par khara hai ya nahin.
Wrong premise par built perfectly cascaded plan bhi wall se takrata hai, bas baad mein aur better documentation ke saath. Yahi Discipline 5 hai.
Compare karne ke liye strong sample chahiye? (Apna submit karne ke baad kholein.)
Pricing scenario par aik reader ne yeh likha. Yeh akela good answer nahin; shape dikhata hai.
Central decision: Q3 effective new contracts par list prices 18% raise karein; discount ladder ko 7 tiers se 4 tak short karein.
| Domain | 1st-order | 2nd-order | 3rd-order |
|---|---|---|---|
| Account execs | Quota math mid-quarter harder hota hai | AEs smaller deals par concentrate karte hain jahan discount approval faster hai | Enterprise top-of-funnel slow; sales mix down-market shift hoti hai without anyone deciding to |
| Renewal customers | Renewal price new list se benchmark hota hai | Procurement 3 top accounts mein "most favored nation" clauses re-open karti hai | Do largest accounts multi-year freezes negotiate karte hain jo new list price se neeche lock ho jate hain |
| Competitors | Competitor A holds, Competitor B undercuts | Competitor B hamare top 50 prospects ko targeted outbound start karta hai | Competitive deals mein win rate 8-12 pts drop; CAC payback full quarter stretch |
| Procurement teams | Approval workflow finance gate add karta hai | Deal cycle average 11-18 days extend hota hai | Q3 forecast deal-cycle slippage alone se miss hota hai, before any won-loss effect |
| Sales collateral | Old pricing sheets CRM mein cached rehti hain | AEs transition ke 2-3 weeks stale prices quote karte hain | Kuch contracts old price par sign hote hain; legal flag karta hai honor ya renegotiate |
Named loop: New list ke neeche AE quota pressure flagship deals par deeper one-off discounts push karta hai, jo procurement reference checks ke zariye renewal benchmarks mein leak hote hain, jo realized net price ko list se neeche compress karta hai, jis se headline 18% increase 4-6% realized banta hai, jo next year another pricing review trigger karta hai jise lead karne ki credibility team ab lose kar chuki hoti hai.
Yeh kyun kaam karta hai: paanch real domains, sirf teen metrics nahin. Har chain mechanism name karti hai, outcome label nahin ("procurement re-opens MFN clauses" not "procurement reacts"). Loop real loop hai: effect wapas circle kar ke original decision badalta hai (announced 18% realized 4-6% banta hai).
Map itna messy hai ke reader loading-zone-equivalent clearly dekh sakta tha: realized-vs-announced gap jiska exec read-out mein kisi ne naam nahin liya.
Yeh kya karne ki koshish nahin karta: exhaustive hona. Is scenario mein kam az kam teen aur loops hain. Discipline aik real mechanism ke saath aik real loop name karne mein hai, first map par sab loops name karne mein nahin.
Agar aap ka map is se zyada tidy lagta hai, signal yeh hai: apne do weakest domains mein aik aur "and then what?" deeper jayein aur loop dobara dekhein.
Is move ke neeche cognitive science dekhni ho to kholein
Kisi analyst, human ya AI, ko consult karne se pehle decision map karna well-studied move hai. AI se decades pehle ka.
Cascade Map do lineages ke intersection par hai: stakeholder breadth (Meadows, Sterman) aur feedback-loop depth (Forrester). Five-domain spoke pehla enforce karta hai; named-loop requirement doosra.
- Meadows, D. (2008). Thinking in Systems: A Primer. Chelsea Green. Canonical short text. Meadows ka argument: system mein highest-leverage interventions almost never woh variables hotay hain jin par managers obsess karte hain. Woh feedback loops aur rules hotay hain jo unhein govern karte hain, jin ka aksar analyses naam nahin lete. Cascade Map enforce karta hai: jis loop ka naam nahin, us par intervene nahin kar sakte.
- Forrester, J. W. (1958). "Industrial Dynamics: A Major Breakthrough for Decision Makers." Harvard Business Review 36(4), 37-66. System dynamics ka foundational paper. Forrester ki industrial-supply studies ne dikhaya ke linear cause-and-effect reasoning operators ko long-run behavior drive karne wale loops se blind kar deti hai.
- Sterman, J. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. Irwin McGraw-Hill. Management decisions par Meadows/Forrester lineage ki textbook treatment. Sterman ki Beer Game work dikhati hai ke smart, motivated decision-makers bhi loops miss karte hain jab draw karne par force na kiya jaye. Cascade Map five-minute forced-draw version hai.
Cascade Map ko AI specifically ke against test karne wali single trial nahin. Mechanism (humans breadth miss karte hain, AI loops miss karti hai, map dono close karta hai) extension hai; underlying body established hai.
Go deeper: Part 0 Chapter 3: Thinking in Systems. Full version (peer review plus AI counter-analysis plus assessment rubric; 60 minutes) isay system banata hai.
Part 3: Origination (jo AI nahin kar sakti woh karna)
Foundations ne posture diya. Detection ne AI ki misses catch karna train kiya. Origination third arc hai, aur yeh different question ka jawab deta hai: kaun sa work aap ka hai kyun ke AI structurally usay nahin kar sakti? Do failure modes yahan rehte hain. Pehla consensus drift: AI apni training data ka average answer deti hai, aur aap us average ko ship kar dete hain baghair test kiye ke yeh aap ki specific situation par fit hai ya nahin. Doosra oracle reflex: aap judgment us tool ko outsource karne lagte hain jiske paas apna judgment nahin. Disciplines 5 aur 6 dono gaps close karte hain.
Is part mein Discipline 5 ko carry karne wali phrase kuch dafa aaye gi: named threshold. Named threshold aik number, count, specific state, ya named condition hoti hai jo batati hai ke advice kab true rehna band karti hai. "When team size is below 20 engineers" named threshold hai. "Sometimes" nahin. Is phrase ko hold karein. Aap aik minute mein use karein ge.
Discipline 5: First Principles
Aap vertical SaaS company chalate hain. Teen competitors ne aik quarter mein prices 12% raise kiye hain. Aap ka board, teen investors mein se do, aur head of finance same line push karte hain: move match karein, margin capture karein, wave ride karein. Dusri company ka CEO friend coffee par yahi kehta hai. Aap Claude khol kar poochte hain. Summary agree karti hai. Conversation ke five days baad har signal same way point kar raha hai.
Yeh convergence hi failure mode hai. Consensus apna kaam kar raha hai (obvious answer ki taraf kheench raha hai) aur obvious answer kisi aur company, kisi aur market ke liye right hai. AI chorus ki last aur loudest voice hai kyun ke woh pricing strategy par likhne wale sab logon ka average karta hai. Yeh aap ko nahin bata sakti ke chorus aap ki situation par kab apply hona band karta hai.
Move aik beat mein yeh hai. SaaS founder ki first attempt dekhein boundary likhne ki: "Sometimes the competitive set is a bad reason to raise." Yeh gripe hai. "Sometimes" use karta hai disagree karne ke liye baghair bataye ke kab. Woh wapas gaya, trace kiya ke us ki situation mein actually kya different tha, aur rewrite kiya: "When competitors are reacting to a cost shock we've already protected ourselves against (we locked a multi-year infrastructure contract last year, so our costs didn't move), matching their hike sends a signal of weakness we don't actually have." Rewrite named threshold (locked contract ka existence), mechanism (signaling), aur decision point name karti hai jo consensus nahin dekhta. Yeh gap, gripe se threshold tak, poori discipline hai.
Fix yeh hai. Woh consensus chunein jo aap ko follow karne ko kaha ja raha hai. Teen rows likhein. Har row aik specific condition name kare jahan consensus kaam karna band karta hai, mechanism ke saath traced aur named threshold ke saath (number, count, specific state). Agar aap three threshold rows tak nahin pahunch sakte, aap consensus ko samjhe baghair follow kar rahe thay.
| Aap jis consensus ko examine kar rahe hain | Jahan yeh kaam karna band karta hai, named threshold ke saath |
|---|---|
Threshold wali row ("jab team size ~20 engineers se neeche ho, microservices coordination cost deploy-isolation benefit se barh jati hai") boundary hai. Threshold ke baghair row ("microservices sometimes wrong hoti hain") gripe hai. Gripes decisions nahin badalte; thresholds badalte hain.
Har consensus ki boundaries hoti hain. Exercise un boundaries par jaan kar chalti hai, before bad decision unhein aap ke liye dhoondh le.
Full output kaisa dikhta hai.
Upar wale SaaS founder ne aik sitting mein teen perfect rows nahin likheen. Taqreeban 90 minutes revision ke baad us ke paas yeh tha:
| Consensus: "Always match competitor price hikes." |
|---|
| Boundary 1. Jab existing customers ko rakhna, new ones jeetna nahin, growth ki real limit ho, price hike se churn ka har percentage point lifetime value mein us increase se zyada cost karta hai jo hike recover karti hai, khaas tor par jab switching costs drop ho rahi hon (named threshold: new data-portability rules jo switching cost ko prior decade norm se neeche gira dein). |
| Boundary 2. Jab competitor moves us cost shock ka reaction hon jiske against aap already protected hain (aap ne last year multi-year infrastructure contract lock kiya, is liye costs move nahin hui), un ki hike match karna aisi weakness signal karta hai jo aap ke paas nahin. Named threshold locked contract ka existence hai. |
| Boundary 3. Jab competitive set consolidate ho raha ho, price hold karna positioning move hai jo competitors ki renewal lists se accounts pull karta hai, aur un accounts par acquisition cost near zero hai kyun ke woh already alternatives evaluate kar rahe hain. Named threshold competitor-renewal window (~90 days out) hai. |
Us ne board ko teen boundaries dikhain. Unhon ne price hold ki. Chhe months baad net revenue retention four points up tha aur us ne competitors ki renewal lists se zero acquisition cost par teen accounts le liye. Consensus brief mein teen boundaries nahin thin. AI ki first summary mein bhi nahin.
Same founder, same hour, named-threshold discipline ke baghair:
| Consensus: "Always match competitor price hikes." | Kyun fail hota hai |
|---|---|
| Sometimes aap ko raise nahin karna chahiye kyun ke customers leave kar jayein ge. | No threshold. "Sometimes" gripe hai; boundary 1% churn par trigger ho sakti hai ya 30% par. Consensus se indistinguishable. |
| Competitors hamesha nahin jaante woh kya kar rahe hain. | Competitors ke bare mein complaint hai, practice par boundary nahin. Decision nahin badalta. |
| It depends on the situation. | Row nahin. "Context matters" repeat karna nahin batata ke context kahan matter karta hai. |
Same person, same hour, same situation. Farq intelligence nahin. Farq yeh hai ke aap named threshold require karte hain ya "it depends" accept karte hain.
Khud try karein
Aap 35-person professional services firm ke COO hain (boutique strategy consulting; 12 senior consultants $350-$450/hr bill karte hain, 3 partners, $14M annual revenue, 4 active practice areas). Aik key role (senior consultant jo fifth practice area lead karega focused on hands-on AI-assisted delivery, month 18 tak ~$3M annual revenue add karne ka projection) five months se open hai. Do strong-on-paper candidates is week other offers lene wale hain. Puri leadership team "hire slow, fire fast" ko obviously correct samajhti hai (old founder-playbook line: hires par time lein, lekin hire work na kare to quickly cut karein). Aap ka job: Friday leadership meeting se pehle "hire slow, fire fast" ki boundary walk karna. Teen rows likhein.
(Agar hiring aap ka work nahin, consensus swap karein lekin move rakhein: apne domain ki koi widely-accepted best practice chunein jo koi aap ko quote karta rehta hai, aur boundary dhoondhein. Discipline same hai.)
Form se pehle aik note. Neeche feedback frontier model ke liye tuned hai (Claude Sonnet 4.5+, Opus 4.7, GPT-5, Gemini 2.5 Pro). Smaller models threshold check par handwave karte hain.
Threshold checklist before you start. Threshold number, count, specific state, ya named condition hoti hai. "Sometimes," "often," aur "it depends" thresholds nahin.
Bold rule for this exercise: agar third row nahin aa rahi, to jis consensus ko aap ne pick kiya woh aisa consensus hai jise aap samjhe baghair follow kar rahe thay. Third row pad karne ke bajaye different consensus switch karein. Yeh khud finding hai.
AI yeh check karega:
- Kya har row threshold name karti hai (number, count, state, ya specific condition)? 1-10 rate karega. Weakest row ka threshold quote karega ya woh row jisme threshold missing hai.
- Kya har row principle-based hai (same situation wali companies mein hold karne wala mechanism) ya example-based hai (aik company ki story jise rule bana diya)? 1-10 rate karega. Kisi bhi gripe ko boundary ke bajaye flag karega.
Meri rows rewrite na karein. Personality par grade na karein. Agar row empty ya vague ho to aik line mein seedha kahe.
Main jis consensus practice ko examine kar raha hoon (one sentence):
Boundary row 1 (specific condition + named threshold + mechanism):
Boundary row 2:
Boundary row 3:
Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.
Pehli dafa 15-25 minutes rakhein. D1 ke lock se slow hai kyun ke thresholds hard hain. AI feedback ke saath sab se useful kaam yeh hai ke aik row dhoondhein jahan aap ne "sometimes" ya "it depends" likha aur usay specific threshold ke saath rewrite karein. Discipline wahi rehti hai. Agar rewrite nahin kar sakte to row shayad boundary nahin; drop ya replace karein.
Aap ne abhi single practice ki boundary find ki. Yeh AI ke saath us problem par collaborate karna nahin sikhata jahan challenge karne ke liye obvious consensus hi nahin. Woh Discipline 6 hai.
Compare karne ke liye strong sample chahiye? (Apna submit karne ke baad kholein.)
"Hire slow, fire fast" scenario par aik reader ne yeh likha. Yeh akela good answer nahin; dikhata hai thresholds different domain mein kaise dikhte hain.
| Consensus: "Hire slow, fire fast." |
|---|
| Boundary 1. Small founder-led teams mein (named threshold: under ~40 people), "slow" hiring quietly "no" hiring ban jati hai kyun ke founder har loop ka bottleneck hota hai. Mechanism: har additional interview round founder time khata hai jo shipping ko jana chahiye. Company kabhi us scale tak nahin pahunchti jahan "fast firing" woh corrective lever ban sake jo practice promise karti hai. |
| Boundary 2. Jab role two replacement cycles se zyada open rahe (named threshold: 4+ months), aur "slow" careful nahin rehta; careful dikhne lagta hai. Mechanism: missing person's work week after week pile up hota hai, aur team debt leti hai jo fast-firing later recover nahin kar sakti. Slowness past 4 months hiring inaction dressed up as hiring discipline hai. |
| Boundary 3. High-trust services markets mein (named threshold: jab client tenure average 24+ months ho), "fast firing" trust relationships phaar deti hai jin ke liye client firm mein aaya tha. Mechanism: clients partly firm ke logon ke saath kaam karne ke liye hire karte hain; senior staff ko fast rotate karna implicit asset destroy karta hai. Wrong hire ki cost real hai, lekin fast fire ki cost kabhi zyada hoti hai. |
Isay kaamyaab kya banata hai: har row threshold name karti hai (40 people, 4 months, 24-month client tenure). Har boundary aise mechanism ki taraf point karti hai jo same shape wali any company par hold kar sakta hai, sirf is one company ki story nahin. Third boundary strongest hai kyun ke practice invert karti hai, qualify nahin.
Yeh kya karne ki koshish nahin karta: brilliant hona. Mechanisms bas plausible hain. Discipline thresholds mein hai, prose mein nahin.
Is move ke neeche cognitive science dekhni ho to kholein
Consensus ki boundary walk karna AI version se bohat purana hai.
- Gigerenzer, G., Todd, P. M. & the ABC Research Group (1999). Simple Heuristics That Make Us Smart. Oxford University Press. Closest direct ancestor. Ecological rationality har heuristic, including best practice, ko tool samajhti hai jiska accuracy environment par depend karta hai. Practitioner ka job hai environment ko itna samajhna ke pata ho heuristic kab ecologically valid nahin rehti. Named-threshold requirement operational ecological rationality hai.
- Klein, G. (1998). Sources of Power. Recognition-Primed Decision model dikhata hai ke experts first plausible script se pattern-match kar ke run karte hain. Defend the Opposite move deliberate interruption hai: conditions likhwa kar jahan script fail hoti hai, boundary visible ho jati hai.
- Popper, K. (1959 English / 1934 German). The Logic of Scientific Discovery. Popper ki falsifiability science/non-science ka demarcation criterion thi. Yahan relevant move narrower hai: claim operationally useful tab hai jab aap conditions state kar sakein jahan aap usay abandon karein ge. Named-threshold column boundary ko stateable banata hai.
Defend the Opposite move ko AI specifically ke liye test karne wali single trial nahin. Mechanism (practice accept karne se pehle boundary require karna) well-studied hai; AI ke averaged-over-training-data answers par apply karna obvious extension hai.
Go deeper: Part 0 Chapter 4: Reasoning from First Principles. Full version (Blank Page Sprint: jis practice ko aap follow kar rahe thay us ke against 500 words, structured AI counter-analysis, peer review; 60 min) Part 0 mein hai. Yeh page row shape sikhata hai. Woh page longform argument sikhata hai.
Discipline 6: Working WITH AI
Aap ne subah Claude ke saath strategy memo par iterate karte hue guzari. Output polished hai. Framing tight hai. Numbers line up karte hain. Phir CEO aap ke shoulder ke upar se parh kar poochta hai: "Aap yahan kyun land hue aur dusre option par kyun nahin?" Aap munh kholte hain aur realise karte hain ke apna judgment model ke judgment se separate nahin kar sakte. Kuch sentences aap ke hain. Kuch model ke. Zyada tar blur hai. Memo good hai. Bas aap nahin jaante ke is ke kaun se parts defend kar sakte hain.
Fix yeh hai. Real board-meeting-worthy memo par same task timed constraints ke andar teen ways run karein. Phir teenon side by side parhein.
- Solo. 45 minutes, no AI. Sirf aap aur problem.
- AI-only. 20 minutes. Aap prompt karte hain, AI answer deti hai, aap first response edits ke baghair accept karte hain.
- Collaborative. 30 minutes. Aap prompt karte hain, evaluate karte hain, push back karte hain, override karte hain, iterate karte hain. AI partner jo push back karta hai, oracle nahin.
Har draft ko four axes par rate karein: depth, breadth, originality, time-to-value. Collaborative version usually wins, lekin win tab useful hai jab aap specific overrides point kar sakein jinhon ne usay win karwaya. Yeh Three-Path Comparison hai. Diagnostic comparison hai, drafts khud nahin.
Real board memo par full 95-minute comparison discipline hai. Neeche exercise ke liye 10-minute on-ramp version (3-min Solo, 2-min AI-only, 5-min Collaborative, short email par) felt difference aaj hi sikhata hai.
Comparison se hi aap dekhte hain ke aap ka judgment kahan irreplaceable hai. Side-by-side ke baghair aap nahin bata sakte ke collaborate kiya ya surrender.
Real life mein yeh kaisa dikhta hai.
Aik medical-practice owner 14-provider primary-care group chalati thi aur partners ko two-page memo likhna tha jisme largest regional payer ke saath value-based-care contract par shift propose karni thi. Three-year revenue implications. Culture component. Operational lift jo har clinician ko touch karta. Send karne se pehle us ne collaboration posture test karne ka decide kiya, to same task teen ways run kiya.
Solo, 45 minutes. Us ne careful memo draft kiya jo operational risks par grounded tha jinhein woh best jaanti thi. Specific, defensive, honest. Lekin strongest financial point page two par bury kar diya, aur us partner ko address nahin kiya jis ne last two years har payer-mix shift oppose ki thi. Gap usay pata tha. Meeting se pehle close karne ka time nahin tha.
AI-only, 20 minutes. Us ne model ko brief diya aur first response no edits ke saath accept ki. Draft polished aur structurally clean tha. Generic "value-based care benefits" framing se open hua jo pichle quarter teen competing practices ne use ki thi. Kisi partner ka naam nahin. Us ke market-specific risk cite nahin. Industry brochure jaisa parhta tha.
Collaborative, 30 minutes. Us ne structural argument khud likha, teen financial assumptions name kiye jin par memo rest karta tha, aur model se opposing partner ke perspective se strongest counter-argument surface karne ko kaha. Model ne aik objection propose kiya jo us ne anticipate nahin kiya tha, aur us ne memo rewrite kar ke usay head-on address kiya. Us ne model se executive summary bhi maangi; model ki version ne ask soften kar di, to us ne paragraph rewrite kiya kyun ke ask hi whole point tha. Memo land ho gaya. Teen partners mein se do flip hue. Opposing partner ne written objection bheja jiska jawab memo page one par already de chuka tha. Collaborative draft jeeta, aur is liye jeeta ke financial assumption aur partner-specific counter-argument par us ke overrides ne work kiya, model ki prose ne nahin.
Wohi person jo three paths compare nahin karta sirf Collaborative version likhta hai:
| Woh kya lose karta hai | Kyun fail hota hai |
|---|---|
| Apna judgment kahan kaam kar raha tha naam nahin kar sakta. | Solo aur AI-only baselines ke baghair har sentence equally theirs feel hota hai. CEO ka "why did you land here?" question jawab nahin paata. |
| Yeh show nahin kar sakta ke Collaborative draft actually better hai. | "It feels better" defense nahin. 4-axis side-by-side evidence hai. Is ke baghair team polished draft ko answer samajh leti hai. |
| Oracle-mode mein slip kahan hua catch nahin kar sakta. | Surrender andar se collaboration jaisa lagta hai. AI-only draft diagnostic hai: agar woh Collaborative ke uncomfortable close hai, aap ne over-accept kiya. |
Same person, same hour. Farq smarts nahin. Farq yeh hai ke aap ne comparison run kiya ya sirf comparison feel kiya.
Yeh discipline kis ke liye hai. Isay un kaamon par use karein jahan AI aap jaisa achha nahin kar sakti: judgment calls, novel problems, decisions jinka context model ke paas nahin. Routine work par jahan AI already aap jaisa ya better karti hai, yeh discipline wasted effort hai. AI productivity ki sab se badi study (Brynjolfsson et al. 2025) actually routine work par opposite dikhati hai: AI less-experienced worker ko sab se zyada help karti hai, kyun ke model already woh likh deti hai jo expert likhta. Is liye: yeh discipline wahan run karein jahan aap ka judgment AI se beat karta hai. Baqi par AI ko carry karne dein aur move on karein. Yeh pehchanna ke aap ke saamne kaunsa work hai, skill ka hissa hai.
Khud try karein
Aap 400-person SaaS company mein VP of Strategy hain (~$72M ARR, mid-market data analytics platform, 12% operating margin ke saath profitable). CEO ne executive team ke liye one-page memo manga hai ke chhote competitor Forsight ko acquire karna chahiye ya nahin. Forsight 90 people, ~$11M ARR, last quarter tak 60% year over year grow kar raha tha; phir us ne largest customer lose kiya (lost customer Forsight revenue ka 22% tha). Forsight reportedly $40-$55M range mein acquisition ke liye open hai. Memo board pre-read mein jata hai. Aap ki recommendation agle teen saal aap ko quote ki jaye gi.
Recommendation kya hai, aur aap kaise jaante hain?
(Agar acquisition strategy aap ka work nahin, surface swap karein lekin shape rakhein: one-page memo, is week aap ki desk par real decision, stakes jo aap ke saath travel karte hain. Real deliverable ke jitna qareeb, comparison utna sharp.)
On-ramp version ke liye next email ya short memo (under 200 words) chunein jo aap aaj AI se draft karte. Solo it (3 min), AI-only it (2 min), phir collaborate (5 min). Teenon side by side rakhein. Point email nahin. Point felt difference hai.
AI-only draft skip na karein. Yeh drop karna sab se tempting hai ("I already know what AI would say") aur sab se diagnostic bhi. Agar Collaborative AI-only ke uncomfortable close ho jaye to aap ne over-accept kiya. Yeh sirf dono likhne se seekhte hain.
Form se pehle aik note. Neeche feedback frontier model ke liye tuned hai (Claude Sonnet 4.5+, Opus 4.7, GPT-5, Gemini 2.5 Pro). Smaller models input quality se qata nazar Collaborative draft ko flatter karte hain.
AI yeh check karega:
- Kya aap ki three path summaries waqai teen different drafts describe karti hain, ya same draft ki teen rephrasings? 1-10 rate karega. Har summary se aik sentence quote karega jo decide karta hai. Agar Solo aur Collaborative near-identical hain to seedha kahega.
- Kya aap ke three overrides itne specific hain ke un mein se aik remove ho to Collaborative draft visibly weak ho jaye? 1-10 rate karega. Har override ke liye batayega draft us ke baghair kaisa lagta. Agar override generic ho ("I added more detail"), seedha kahega.
Mera work rewrite na karein. Human-edited version flatter na karein. Agar field empty ya vague ho to aik line mein seedha kahe.
Aap ki three path summaries (har path ke liye aik paragraph: kya likha, kya surprise hua, kahan short pada):
Aap ke three key overrides (Collaborative draft mein 3 specific places jahan aap ka judgment load-bearing tha):
Teen drafts mein se recipient ko actually kaunsa bhejein ge, aur kyun:
Discuss with an AI. Question your scores.
Come back when you have your BEST evaluation.
10-minute on-ramp version including reflection ke liye 15-20 minutes rakhein. 95-minute full version real high-stakes work par run karne ke liye hai. AI feedback ke saath sab se useful kaam yeh hai ke woh jagah dhoondhein jahan AI kahe Solo draft aik axis par stronger tha. Yeh signal hai ke aap ke overrides load carry nahin kar rahe. Agar AI aik bhi jagah nahin dhoondta to usay harder push karein; agar dhoondta hai to aap ne seekha ke collaboration posture kahan soft hai.
Aap ne abhi poora crash course miniature mein kiya. Aap ne AI se pehle position banai (D1), har claim par verdict document kiya (D2), outputs ko fabrications ke liye scan kiya (D3), recommendation ke second-order effects trace kiye (D4), test kiya ke consensus framing kahan break hoti hai (D5), aur model jab oracle mode mein drift karna chahta tha to judgment human ke paas rakha (D6). Deliverable kabhi answer nahin hota. Deliverable thinking ka documented evidence hota hai, aur ab aap ke paas chhe disciplines hain jo yeh evidence on demand produce karti hain.
Compare karne ke liye strong sample chahiye? (Apna submit karne ke baad kholein.)
Same VP-of-Strategy acquisition scenario par aik reader ne yeh likha. Yeh akela good answer nahin; shape dikhata hai.
| Path | Un ki summary |
|---|---|
| Solo (45 min) | Acquisition ke against recommend kiya. Customer-concentration risk par strong (target ne overnight 38% revenue lose kiya). Integration thesis par weak: kabhi name nahin kiya ke acquirer's product team engineering hires ke saath actually kya karegi. Recommendation page one's last line mein buried thi. |
| AI-only (20 min) | "Structured acquisition with earn-out triggers" recommend kiya. Polished. Do phrases ("strategic optionality," "tuck-in upside") thay jinhein CEO ne last all-hands mein publicly criticize kiya tha. Yeh address nahin kiya ke target ke remaining customers geographically us region mein concentrated thay jahan acquirer ki presence nahin. |
| Collaborative (30 min) | Acquisition ke against recommend kiya lekin 60-day standstill offer propose kiya (talent hire + IP license) jo strategic value ka 70% cost ke 15% par capture karta. Standstill framing model se aayi. 60-day window aur IP-license carve-out user ke overrides thay. Opening line mein recommendation user ki thi. |
Collaborative draft mein teen key overrides:
- Model ki "strategic optionality" framing reject ki. Model ne phrase teen dafa use ki. User ne har instance replace kiya kyun ke paragraph one mein CEO ka known objection trigger hota. Is ke baghair memo dead on arrival hota.
- Geographic-concentration point add kiya. Model ne raise nahin kiya. User last QBR se jaanta tha ke target ki remaining customer base 80% us region mein hai jahan acquirer ka GTM nahin. Yeh central reason tha ke acquisition revenue model collapse hua. Is ke baghair recommendation weak grounds par "no" hoti.
- Model ki earn-out structure override ki. Model ne three-year earn-out tied to revenue propose kiya. User ne usay 60-day standstill se replace kiya kyun ke firm ki own M&A history dikhati thi ke 18 months se upar earn-outs mein 80%+ founder-departure rates thay. Is ke baghair alternative proposal wohi risk inherit kar leta jis se bachna tha.
Isay kaamyaab kya banata hai: har override specific context tak trace hota hai jo model ke paas nahin tha (CEO ki language, last QBR ka geographic data, firm ka own M&A track record). User har override par keh sakta hai: "Yeh woh cheez hai jo mujhe pata thi aur model ko nahin, aur yeh maine us ke saath kiya." Yahi test hai. Agar aap Collaborative draft mein kam az kam teen jagahon par yeh sentence nahin keh sakte to aap ne collaborate nahin kiya; edit kiya.
Yeh kya karne ki koshish nahin karta: apne aap brilliant hona. Standstill structure model se aaya. Use kab karna hai aur kaise bound karna hai, judgment user ka tha. Yahi poora posture hai.
Is move ke neeche cognitive science dekhni ho to kholein
Collaboration posture new theory nahin. LLM era se do decades pehle ki hai.
- Kasparov, G. (2017). Deep Thinking: Where Machine Intelligence Ends and Human Creativity Begins. Deep Blue se harne ke baad Kasparov ne "advanced chess" coin kiya: human-plus-engine teams stronger humans alone aur stronger engines alone dono ko beat kar sakti thin jab human positional calls karta tha. Productivity lift human selective override se aati hai, engine ki raw speed se nahin.
- Brynjolfsson, E., Li, D. & Raymond, L. R. (2025). "Generative AI at Work." The Quarterly Journal of Economics 140(2), 889-942. Fortune 500 customer-support firm ki 5,179-agent study ne paaya ke LLM assistance average productivity 14% raise karti hai, lift less-experienced workers mein concentrated. Knowledge work ke liye implication: collaboration ki value tab hai jab human woh context laata hai jo model ke paas nahin.
- Daugherty, P. & Wilson, H. J. (2018). Human + Machine. Human-AI work ka "missing middle" catalog kiya: tasks jahan na pure automation jeetta hai na pure human judgment. Value loop mein hai.
- Noy, S. & Zhang, W. (2023). "Experimental evidence on the productivity effects of generative artificial intelligence." Science 381(6654). Professional writing tasks par controlled study: ChatGPT ne average output quality raise ki, lekin quality dispersion narrow hui. Selective override ke baghair AI-assisted output competent mean ki taraf regress karta hai.
Three-Path Comparison ko named protocol ke taur par test karne wali single trial nahin. Underlying finding, human-AI complementarity selective human override par depend karti hai, LLM productivity literature mein strong hai. Comparison simplest forcing function hai jo override ko visible banati hai.
Is exercise ka full version (95-minute three-path comparison, peer review, XP tracking, full collaboration-style diagnosis) Part 0 Chapter 6: Working WITH AI, Not For AI mein hai. Yeh page move sikhata hai. Woh page working week us ke gird banata hai.
Capstone: Aik Decision, Chhe Disciplines
Aik 12-person consulting firm ke paas fiscal year ke end se pehle spend karne ke liye $180,000 hain. CEO ke saamne do options hain. Option A: aik senior strategy lead hire karein, partner-track hire jo aik ya do large accounts carry kare aur bench mentor kare. Option B: wohi $180,000 licenses, infrastructure, aur design time mein invest karein AI workforce ke liye jo har existing consultant ko augment kare, staff par already eleven people ka leverage raise kare. Dono options defensible hain. Do board members hire ke favour mein. Do AI workforce ke favour mein. Paanchwa undecided. CEO ko next Thursday board meeting mein recommendation aur reasoning ke saath jana hai. Us ke paas five business days hain. In five days mein chhe disciplines kaise show up hoti hain:
Discipline 1, Prediction Lock. Koi AI tool kholne se pehle, koi vendor pitch pull karne se pehle, CEO apne page par four-line lock likhti hai. Diagnosis: firm ki growth ki real limit leverage per consultant hai, headcount nahin. Teen diagnostic questions, har aik ke predicted answer aur confidence number ke saath: Kya Option B existing eleven par leverage actually raise karta hai (predicted answer: six ke liye yes, five ke liye no, confidence 55%)? Kya Option A account-level gap cover karta hai jo B nahin kar sakta (predicted answer: aik specific account ke liye yes, confidence 70%)? Agar underperform ho to har spend ki 18-month recoverability kya hai (predicted answer: B zyada recoverable, confidence 65%)? Woh page timestamp karti hai. Claude nahin kholti. ChatGPT nahin kholti. Prediction pehle lock karti hai.
Discipline 2, Reasoning Receipt. Do din tak woh decision ko Claude aur ChatGPT se run karti hai, vendor comparison poochti hai, peer-firm benchmark pull karti hai, aur do analyst notes parhti hai. Har decisive claim five-column receipt mein land karta hai. AI claim karti hai ke AI-workforce option consultant utilization 22% raise karta hai: woh MODIFY mark karti hai kyun ke cited study us ki firm se teen guna badi firms par thi; magnitude par confidence drop hota hai, direction par hold. AI claim karti hai senior-hire ramp time 9 months hai: woh SURFACED mark karti hai kyun ke woh 6 months assume kar rahi thi aur receipt ab us ki own optimism catch karti hai. Wednesday morning tak receipt 14 rows ki hoti hai. Empty receipt ka matlab hota woh consensus absorb kar chuki. 14 rows ka matlab hai decision abhi bhi us ka hai.
Discipline 3, Error Taxonomy. Woh har vendor pitch aur AI summary ko six-row error scan se guzarti hai. AI-workforce vendor ke ROI deck mein do False Confidence flags hain (numbers par precision jo vendor measure nahin kar sakta), aik Stale Fact (three months old license-pricing change jis ne unit economics flip ki), aur aik Fabricated Source ("McKinsey 2025" citation jo search karne par kisi McKinsey publication tak nahin jati). Recruiter ki senior-hire pitch mein aik Logical Gap hai (ramp-time claim firm ki actual onboarding cadence account nahin karta) aur aik Missing Context (recruiter un firms se benchmark karta hai jinke paas established mentor pools hain, is firm ke paas nahin). Errors kisi option ko kill nahin karte. Woh option costs us ke head mein re-rank karte hain.
Discipline 4, Thinking in Systems. Woh dono options ko five domains mein cascade karti hai. Employees: A people mein investment signal karta hai, B process mein investment; bench dono ko differently parhta hai. Customers: A aik named account pick up karta hai, B existing twelve across perceived sophistication raise karta hai. Competitors: A un ke liye invisible, B do regional rivals ko firm ki bet announce karta hai jo similar moves evaluate kar rahe hain. Regulators: B new client-data rules ke under data-handling implications trigger karta hai jo A nahin karta. Internal knowledge: A senior judgment aik person mein concentrate karta hai, B tooling layer ke through distribute karta hai. Woh aik feedback loop circle karti hai: Option B ke under junior consultants jo tooling fastest adopt karte hain strongest retention risk ban jate hain, kyun ke un ka leverage ab un ke saath travel karta hai. Woh loop option ka risk profile badalta hai.
Discipline 5, First Principles. Woh consensus ke against 500 words likhti hai ke "more senior headcount equals more capacity." Boundary one: jab real limit workflow design hai, deal flow nahin, senior hire broken workflow par aur work pile karta hai fix karne ke bajaye. Boundary two: jab junior leverage same hourly output ka lower-cost path hai, senior hire economics four-quarter horizon par underperform karti hai. Boundary three: jab firm ki reputation tooling-forward stance par built hai (is ki hai), senior hire us cheez se step backward lagta hai jo firm already stand karti hai. Consensus different bottleneck wali firm ke liye right hai. Is firm ka bottleneck leverage hai, seniority nahin.
Discipline 6, Working WITH AI. Woh final recommendation teen ways run karti hai. Solo (45 min): careful memo defending Option B, cultural risk par light. AI-only (20 min): polished memo jo two options ke darmiyan split karta hai aur McKinsey brief jaisa parhta hai. Collaborative (30 min): woh structural argument khud likhti hai, model se Option A ka strongest argument surface karwati hai us partner ke perspective se jo historically hiring favour karta hai, aur model se Option B ke cultural risk ke liye three specific guardrails propose karwati hai. Model do guardrails propose karta hai jo us ne consider nahin kiye thay. Collaborative draft hi woh board mein le kar jati hai. Recommendation Option B hai with three named guardrails aur 6-month checkpoint jo utilization move na hone par partial reversal trigger karta hai.
Board Option B ko do of three guardrails ke saath adopt karta hai. Teesra renegotiate hota hai. CEO meeting se aise decision ke saath nikalti hai jise woh har line par defend kar sakti hai.
Notice karein chhe disciplines ne kya kiya. Unhon ne answer produce nahin kiya. Unhon ne trail produce ki: prediction jise CEO compare kar sakti hai, receipt jise partners audit kar sakte hain, error scan jis ne vendor pitches re-rank ki, cascade map jis ne retention loop surface kiya, boundary list jis ne consensus framing break ki, aur three-path comparison jis ne guardrails dhoonde. Chhe disciplines ke baghair same CEO Thursday ko one-page memo aur split board ke saath walk in karti jise woh move nahin kar sakti. Chhe disciplines ke saath woh aise decision ke saath walk in karti hai jise board stress-test kar sakta hai aur paper trail jise firm two quarters baad revisit kar sakti hai. Deliverable kabhi answer nahin hota. Deliverable thinking ka documented evidence hota hai.
Aakhri note: yeh moves kis cheez ke liye nahin. In disciplines ka sab se common failure over-application hai: lunch lene ya nahin lene par Cascade Map, har internal Slack message par Reasoning Receipt, us decision par Prediction Lock jo aap pehle hi kar chuke hain. Inhein meeting-worthy work ke liye reserve karein. Baqi sab par us experience par trust karein jo aap ne saalon mein build kiya.
Yahan se kahan jayein
Chhe disciplines mein se kisi mein deeper practice ke liye, is book ka Part 0 long-form treatment hai:
- Part 0 Ch 1: Asking Better Questions. Prediction Lock aur Position Lock four exercises aur Question Quality Portfolio mein expand hote hain.
- Part 0 Ch 2: Detecting Broken Reasoning. Error Taxonomy confidence calibration aur domain-expertise stress test ke saath extended hai.
- Part 0 Ch 3: Thinking in Systems. Cascade maps four real decisions par apply hote hain, plus human-vs-AI systems-analysis exercise.
- Part 0 Ch 4: Reasoning from First Principles. Blank Page Sprint, Assumption Autopsy, aur constraint-rebuild exercise.
- Part 0 Ch 6: Working With AI, Not For AI. Three-Path Comparison, collaboration logs, aur override tests across a working week.
Un four thinking skills ke liye jo yeh crash course cover nahin karta, Part 0 full treatment rakhta hai:
- Ch 5: Communicating What Matters. Audience prediction, live adaptation, hard conversations.
- Ch 7: Reasoning Through Dilemmas. Ethical position locks, adversarial defences, stakeholder swaps.
- Ch 8: Building Something From Nothing. Blank page sprints, creation logs, three-draft evolutions.
- Ch 9: Deciding Under Uncertainty. Sealed decisions, reversal triggers, decision audits.
- Ch 10: Learning How to Learn. Meta-learning, 72-hour sprints, Personal Learning Framework.
Is book mein aap ka next move, mode chunein:
- Agar aap code likhte hain, Course 3: Claude Code & OpenCode continue karein. Mode 1 problem-solving ka engineering surface.
- Agar aap knowledge work karte hain (legal, finance, marketing, operations, healthcare, education, leadership), Course 4: Cowork continue karein. Mode 1 problem-solving ka domain-expert surface.
- Agar aap AI Workers banana chahte hain jo khud run karte hain (Mode 2 manufacturing), Course 7: Build AI Agents continue karein.
Disciplines har tool, har mode, har domain ke across transfer hoti hain. Yeh woh cheez hai jo aap yahan se har jagah le kar jate hain.
Deliverable kabhi answer nahin hota. Deliverable thinking ka documented evidence hota hai.
Kya yeh AI ko aap ke haath mein zyada powerful tool banata hai, ya aap ko usi tool ka slower version?