Technical feasibility means judging whether a requested outcome fits available time, budget, systems, and staffing. When expectations exceed those limits, explain the constraints tactfully rather than simply rejecting the request. section 3.7
A strong feasibility response should:
- Describe a specific request that was unrealistic in its manner, cost, or timeframe. section 3.7
- Use factual evidence to explain why the request was not feasible, avoiding subjective opinions. section 3.7
- Offer workable alternatives or compromises and explain how you pursued delivery. section 3.7
Customized customer request
A customer-service representative received a highly customized product request on a short timeframe, bypassing the approved sales process. Instead of saying “That’s not possible,” he thanked the customer, explained that the order required sales involvement, and clarified the process. A stronger response would also connect the constraint to factual delivery limits and propose a workable next step. section 3.7
