Leading AI projects: convening tech teams in government

Three ways to see it

1. 1

   Delivery units exist because line ministries are designed for routine, not for breakthrough. Pakistan's PMRU, Punjab Information Technology Board (PITB), and KPITB each, in different ways, exist to convene specialists, set short delivery cycles, and protect a project from the friction of standard bureaucracy. The civil servant who leads such a unit must do three things at once. First, build a team across reporting lines. Second, define a small, demonstrable outcome that survives a change of minister. Third, manage upward to the chief secretary or the chief minister with an honest cadence of progress and risk.

2. 2

   Building a team across reporting lines starts with a meeting that names the awkwardness aloud. Tell the BS-17 officers that you cannot write their ACR but you can write a letter to their parent department that materially helps their next posting. Tell the contracted engineer that the project will end in 90 days but a successful pilot opens a path to a longer contract. Tell the consultants that their expertise is welcome and their access to citizen data is not unlimited. Naming the asymmetries is what turns a rented team into a real one for a few months.

3. 3

   Defining a demonstrable outcome means trimming. The chief secretary said 'AI-powered citizen-feedback dashboard for all DCs'. By month three, that promise cannot be fully kept. The honest move is to redefine in week one: a pilot covering three carefully chosen districts, one urban, one rural, one mixed; a dashboard with five live metrics that any DC can interpret in two minutes; an SMS-survey integration that the DC's office actually uses, evidenced by week-eight usage logs. The trim is not a retreat. It is the act that protects the project from being declared a failure by month four.

The why-tree

Try this with Claude

AI-edge prompt: 'I am a director general at a Pakistani provincial delivery unit. I have 90 days to ship an AI citizen-feedback dashboard pilot in three districts. My team is hybrid: deputed BS-17 officers, contracted engineers, donor-funded consultants, and a partner IT department. Draft (a) the agenda for my first all-team meeting, (b) the three-section weekly brief template for the chief secretary, (c) a 12-week milestone plan with a forced trim at week one, and (d) a one-page hand-over protocol I will write in week ten.'