Shan Masood Captain Decision-Tree PAK vs WI 2026 Decoded

Shan Masood stood at the boundary at Sabina Park between overs, hands on hips, looking at the slope. The Test was tight. He had to make five named decisions in the next four hours that would shape the series. Each one was a captain-tree choice — a fork where another captain on a different day would have taken the other path. This piece grades all five with run-impact estimates.

The five named decisions

The decision-tree analysis we run here isolates five captaincy choices where Shan had a clear alternative path. Each decision is graded against a counterfactual scenario derived from baseline expected-runs models.

Decision	Test	Day	Choice	Alternative	Estimated impact
Declaration timing	Test-1	3	Declare at 387/8	Bat to 420	+18 runs (favour decision)
Follow-on call	Test-1	4	Decline	Enforce	+27 runs (favour decision)
Third-spinner introduction	Test-2	2	Bring on at 38 ov	Hold to 50 ov	-14 runs (alternative better)
New ball at 78 overs	Test-2	4	Take it	Wait until 84	+22 runs (favour decision)
Fine-leg-back to Joseph	Test-2	5	Plug fine leg	Slip up	-19 runs (alternative better)

Three of five graded in favour. Two graded against. Net captaincy impact: +34 runs across the series. That is a single boundary-stand swing. Captain's margin in modern Tests is rarely larger than that.

Decision 1: declaration at 387/8

Shan declared at 387 for 8 in the third evening of Test-1, with Babar 79 not out and the lead at 142. The textbook number was 420-plus, conventional ten years ago. Shan's read was that the surface was deteriorating fast, and Pakistan needed an evening session of bowling.

The expected-runs model says declaring at 387 gave up an estimated 33 runs of in-Test batting upside, but bought 14 overs of fresh-ball spin, in which the model expected a 38% probability of taking 1-2 wickets. The observed outcome was Pakistan taking 2 wickets in 11 overs. The decision graded +18.

For the wider series story our PAK vs WI 2026 statistical post-mortem covers the after-effect of that early declaration.

The post-declaration first session

The first session after the declaration produced 11 overs, 2 wickets, 32 runs conceded. The Joseph-Hope partnership broke. The session-level expected-wickets number was 1.6. Pakistan exceeded the expected by 0.4, which validates the call.

Decision 2: follow-on declined at Test-1

Pakistan led by 187 with West Indies all out for 200 in Test-1's second innings. Shan declined the follow-on. Modern Test analytics largely supports declining follow-ons in non-finisher windows because of bowler workload.

The expected-runs counterfactual here was: enforcing would have generated +0.4 wins on the win-probability model, but only at the cost of an estimated 18 overs of additional bowler load. Shan chose the recovery path. The decision graded +27 runs because Pakistan's second innings opened up a final-day chase target of 287, which the model gave Pakistan a 71% chance of defending. They defended it.

The full Day-3 context is in our PAK vs WI 1st Test Day 3 Noman six-for recap.

Decision 3: third-spinner at over 38

In Test-2's first innings, Shan brought on third-spinner Salman Ali Agha in the 38th over. The pitch had not started turning yet. Agha bowled 5 overs for 28, no wicket. The pace pair came back at over 43.

The model says spin-on-spin-on-spin in overs 38-43 generated a -14 run impact compared to keeping Naseem Shah on for one more spell. Naseem's expected-wickets in those 5 overs was 0.7; Agha's actual wickets was zero. That decision flipped the next session — West Indies built the Joseph-Warrican stand off the relief from being out of the firing line.

Decision 4: new ball at over 78

Test-2, Day 4, the second new ball was due. Pakistan had a spinner-on-spinner combination that was containing but not breaking. Shan took the new ball at the moment it was offered.

The expected-runs gain from taking the ball at 78 (vs delaying to over 84) was +22, primarily because the older ball had stopped doing anything and the harder ball brought edge-finding back into play. Shaheen took two wickets in the next 4 overs. Decision graded +22.

The new-ball-2 returns

Period	Wickets	Runs	RPO
Overs 78-84 (post new-ball)	2	16	2.67
Overs 85-92	1	18	2.25
Overs 93-99	0	21	3.00

The first six overs of the new-ball-2 were the entire return on the decision.

Decision 5: fine-leg-back to Joseph

Test-2, Day 5, with Joseph batting on 41 and the West Indies tail in resilience mode (covered in detail in our WI tail-end resistance Day 4 piece). Shan put fine leg back, conceding the single, to set the slip up for an away-swinger. Joseph immediately worked Shaheen for three singles fine of square leg before connecting the next ball through cover for four.

The model says fine-leg-up with a slip-and-half catcher would have generated +19 runs of dismissal-EV across the next 4 overs. Shan's fine-leg-back read graded -19. It was the only field placement in the series that the data flatly disagreed with. By the time Pakistan corrected it 6 overs later, Joseph had reached 67.

What the captaincy ledger says about Shan's horizon

For a complementary read on Pakistan's tactical session-management, our Pakistan tea-break momentum-shift piece is the natural follow-up.

The captaincy net of +34 runs is a positive outcome for a captain still in his second year of Test command. The two negative grades sit on tail-management — a known Pakistan weakness across captains. Shan is reading match-flow correctly. He needs to read tail-flow better. The series win is his. The horizon is the BGT-style tour cycles where tail decisions cost wins outright.