Stakeholder Negotiation Planner

Scenario: Pushing back on unrealistic availability requirements Trigger: "My CTO wants 99.999% availability for our internal tool used by 50 employees. That would cost $200K in infrastructure." Process: Classified as business stakeholder negotiation. Primary technique: leverage their grammar by translating availability percentages to cost and downtime impact. Prepared comparison table: 99.9% = 8.7 hours downtime/year at $40K vs 99.999% = 5 minutes downtime/year at $200K. Framed as "what's the cost of each hour of downtime for 50 internal users?" to let the math make the argument. BATNA: implement 99.9% with monitoring, propose revisiting if actual downtime impacts exceed the cost differential. 4 C's check: using cost language (Communication), framing as "let's find the right investment" (Collaboration), specific numbers not vague "it's expensive" (Clarity), two-slide comparison not a 30-page report (Conciseness). Output: Negotiation brief with cost comparison table, opening frame, anticipated objections (e.g., "but what about that outage last year?"), and compromise position at 99.95%.

Scenario: Disagreement with senior developer on architecture pattern Trigger: "The senior developer insists REST is better for everything. He has 15 years of experience." Process: Classified as developer negotiation. Primary technique: demonstration defeats discussion. Prepared a plan for a small proof-of-concept showing the specific scenario where event-driven outperforms REST (e.g., order processing where downstream services don't need synchronous response). Also identified the Frozen Caveman pattern — the senior developer may be defaulting to REST because of a bad experience with messaging years ago. Strategy: acknowledge their REST expertise explicitly, agree REST is appropriate for most of the services (divide and conquer), but propose a POC for the 2 services where async communication has clear benefits. BATNA: implement REST everywhere with the understanding that the 2 high-throughput services may need refactoring later, and document this prediction in an ADR. Output: Negotiation brief with POC proposal, specific service pair for demonstration, acknowledgment language, and ADR template for documenting the decision.

Scenario: Negotiating tech debt vs features with product leadership Trigger: "The product team wants 5 new features. I think we need to address tech debt first." Process: Classified as business stakeholder negotiation (VP of Product). Primary technique: state impacts in cost and time. Translated tech debt to business language: "Each feature currently takes 3 weeks because of the data layer complexity. After a 4-week refactor, each feature would take 1 week. Five features at 3 weeks = 15 weeks. Four-week refactor + five features at 1 week = 9 weeks. The refactor saves 6 weeks and every future feature is faster." Compromise position: do the refactor in parallel with 2 of the 5 features, deferring 3 features by 2 weeks. BATNA: proceed with all 5 features, document the increasing delivery time trend, and revisit when feature delivery time exceeds stakeholder patience. Output: Negotiation brief with ROI calculation, delivery timeline comparison chart, compromise proposal, and risk documentation plan.