A 'Development' Tragedy–Pakistan#7

The Tightening: When the System Shows Its Teeth

Next day, the emails arrived within hours of each other. Coordinated. The first from both K. and M. together – unusual, that joint signature – announcing new communication protocols: All correspondence must now be cc'd to the supervision triad. Regardless of focus. The word "streamlined" doing heavy lifting to disguise what this actually is: a new control structure. Every exchange now monitored, every question now public, every observation now legible to those whose job is contract compliance rather than systems understanding.


The second email, longer, in German – no national colleagues cc'd. Five numbered points that read like an indictment masquerading as clarification. I can feel the overnight conversation between my contractors, the coordination, the decision to formalize what had accidentally been flexible in the contract, to pin down what had been emergent. Power consolidation in real-time.

• Point 1: Focus must be on the Rahim Yar Khan workshop. The results must serve the decision-makers there, contribute to better understanding of systemic risks. This is actually in alignment with what I want to do. But it's framed as a constraint, a boundary, a limitation on what I thought was an exploratory engagement. The language of "shall" and "must" replacing earlier talk of "co-creating" and "emergent process."
  

• Point 2: The volatile situation requires flexibility and adherence to security protocols. The email tries to frame that restrictions were communicated in advance and "the work assignment must be implemented within this framework." This is the reframing of my bus and motorbike journey, my observation that systems need to be encountered rather than managed from hotel offices. An attempt to claim non-compliance with security protocols in hindsight.
  

• Point 3: The rewriting of intention. "In preliminary conversations you expressed a clear preference to spend as much time as possible on the ground – even privately – if it would give you better understanding of the context here." True. Followed by: the two weeks of your stay here aren't fully covered by contract. According to the contract, you have 2 days in Switzerland and 18 days for Pakistan and Botswana combined. "Based on our understanding, the days for Pakistan have by no means been exhausted and should be absolutely sufficient to produce the results specified in the contract."This is the move. The 18 days need to cover both countries. Yet the contract doesn't specify deliverable quantities or time allocations. This is the vagueness in the contract that could be my loophole or my trap, depending on who controls the interpretation. They're moving to control the interpretation.

• Point 4: "Business trips involve unpaid administrative processes that consultants normally handle." 

My comments this week about the time burden of administrative processes like a 1-hour security briefing stand in contradiction to this. The gaslighting is almost perfect. An hour-long briefing that told me nothing I didn't already know, that was pure theater, that exists to protect the organization rather than inform the consultant.

• Point 5: Please send agenda/strategy and slides for next week's workshop by tomorrow. They had their preparation call with the main consultant today and there's a desire to better understand how the second workshop day is designed.

Tomorrow. Agenda, strategy, slides. For a workshop that was badly planned on their side. I had suggested to have it emerge from context, from the contextual knowledge I'm still gathering, from the relationships I'm still building. Now they get insecure and want the deliverable before the process that would produce it. This is the retreat to ctrl+cmd worldview made explicit: input → process → output, all pre-defined, all controllable, all legible to contract monitors who've never been in the field.

I can feel the survival mechanisms activating. The rumination. The defensive scenarios playing out. The anger at being managed like a production unit rather than engaged as a thinking human. The fear that they'll use contract ambiguity to extract robot work while masquerading it as systems thinking. The email reads like having to isolate me like I was the disease – being tacitly marked as difficult, non-compliant, not-team-player. This is structural consolidation. They've moved from individual discipline (yesterday's conversation) to collective management (today's coordinated emails). The cc requirement isn't about communication efficiency – it's about making sure I can't build relationships outside their supervision. Can't go directly to national colleagues. Can't develop the trust-based exchanges where warm data flows.

The Art of War principle surfaces: when the enemy consolidates position, look for the overextension. They're demanding rigidity (deliverables by tomorrow, time allocations pre-defined, all comms monitored) while operating in a context that they themselves describe as volatile and requiring flexibility.

Luckily so far, the contract is my terrain. They're trying to occupy it through interpretation. The contract says:


“Desk Review: Review existing documentation on the XXXXX framework and sectors, its application in the project's geographic focus areas, and related case studies."

Nothing about producing full workshop materials before the desk review is complete. Nothing about time allocation between countries. Nothing about communication protocols. Everything framed as "development" and "engagement" and "co-creation".


But written statements are only as strong as the power to enforce interpretation. And right now they're consolidating that power.

The response I draft in my head swings between extremes:

1. Protective: "You're reinterpreting the contract mid-engagement to extract deliverables never specified. This is scope creep disguised as clarification."

2. Compliant: "Thank you for these clarifications. I'll have preliminary materials ready tomorrow and ensure all future communications follow the stated protocols."


The protective response leads to immediate expulsion. The compliant response feels for me like a death by a thousand cuts, becoming the robot they want while something inside of me curdles.


There's a third way. Make them choose between contradictory positions they're simultaneously holding:


"Are you sure you want agenda and deliverables before the desk review that's specified in contract Phase 1 is complete? Are you sure you want rigid pre-planning in a context you describe as volatile and requiring flexibility? Are you sure you want to allocate fixed days to countries when the contract doesn't specify this division? Are you sure that 'streamlining' communication by adding oversight layers serves the 'co-creation' and 'stakeholder engagement' the contract calls for?"

Each "are you sure?" forces them to either:

• Admit they're changing terms mid-contract

• Acknowledge the contradictions in their demands

• Make explicit the power move they're making implicit


The double-bind is: if they insist, they reveal themselves as rigid contract manipulators. If they soften, they lose the power consolidation they're attempting. Either way, the contradiction becomes visible.

What I know:

• They're afraid. Afraid of liability, of me going off-script, of not having controllable deliverables – cold data – to show their superiors.

• Their fear is making them grip tighter, which makes the system more brittle.

• The volatility they cite as reason for control is actually reason for flexibility, but they can't see this because they're optimizing for institutional protection rather than mission success.

• I’m already marked. The bus travel, the honest feedback, the systems language they don't understand – I'm already in the category of "confusing problem consultant."

The question isn't how to win but what I'm trying to preserve. If it's the contract relationship: play more compliant. If it's integrity and the possibility of learning: push back strategically. If it's gathering intelligence about how these systems defend themselves: document everything and accept that expulsion is probable.


I think I'm trying to preserve the possibility of staying long enough to see the workshop in RYK. To be in that room where decision-makers might actually encounter systems thinking. To gather enough warm data to write something true about how development apparatus functions at the granular level. To make the contradictions visible not just to them but to the wider network of people who need to understand why these interventions consistently fail.

I think about setting up a meeting strategy with their superior:

• Ask them to specify exact deliverables from contract vs. new requests

• Request clarity on time allocation methodology (where is the 18-day split documented?)

• Propose a modified workflow that serves both their need for legibility and the contract's call for stakeholder engagement

• Make them choose: do they want predetermined outputs or do they want systems analysis? Both isn't possible.

• Document everything in writing afterwards.

But first, the email. Professional. Precise. Asking them to be sure about what they're sure about. Making the contradictions do the work rather than my accusations.

Tomorrow I'll know if strategic push-back is possible or if this is the beginning of the end. Either way, I'm still awake. Still seeing. Still refusing to pretend the contradictions aren't there.

The Himalayas are dying. The villages are flooding. The military is the source of all evil but we cannot say that. And in the hotel-like office, the cc requirements proliferate and the agenda deadlines tighten and the system defends itself against anyone who suggests we might be doing something other than what we claim.

Nothing static is ever a thing. They're trying to make it static. This is the death thrashing. I just need to not get caught in it.