CONTEXT · CHOICES · CONSEQUENCES
Learning objective: Explain a decision clearly, check assumptions, and negotiate interests and constraints without relying on stereotypes.
Source status: Course-authored teaching based on a reported topic map. Linked references describe the versions taught here. Original workshop diagrams, homework, and organization-specific procedures were not supplied.
A client asks for an additional feature before a fixed event date. Clarify the underlying interest: is the feature itself needed, or does it support a particular demonstration? Identify constraints, feasible options, and your alternative if no agreement is possible. A negotiation can trade scope, timing, cost, or implementation approach; it need not be a contest to pressure the other side into your original demand.
Try: “For the event, do you need the full workflow or a credible demonstration? We can deliver the narrow demonstration by Friday, or the full workflow next month after testing. What would make either option useful?” Check authority before making a commitment, and record the agreement, exclusions, owners, and next review.
Storytelling can make a technical tradeoff understandable: describe a person facing a problem, the consequence, the choice, and the expected result. To explain technical debt, show how a repeated manual step delays a user's request, then compare a small fix with a rewrite. Include uncertainty and inconvenient evidence. A story should clarify a decision, not replace the evidence behind it.
Limit: plain language is not oversimplification. Keep the material risks and tradeoffs even when you omit implementation detail.
Write a one-minute update about a technical-debt tradeoff for a nontechnical stakeholder. Then ask two open questions for negotiating a new feature against a fixed deadline.
Write your response before comparing it with the example.
0/7000
What is a responsible use of cultural dimensions?
Which negotiation question explores interests?