> ## Documentation Index
> Fetch the complete documentation index at: https://irisdocs.prescientlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Handling Questions & Challenge

> Respond to executive questions with evidence, clear assumptions and appropriate limits rather than bluffing.

Strong consultants do not need an instant answer to every question. They need a disciplined way to respond.

## Use four response types

### Evidence-backed answer

> The interview and workflow evidence both point to the same handoff as the dominant source of delay.

### Assumption-backed answer

> Our base case assumes 60% adoption. That is not observed fact; it is an implementation assumption, so we have shown sensitivity at 40% and 80% as well.

### Product or technical limit

> Iris supports the diagnostic evidence here, but the production integration would need separate technical design before we can confirm implementation effort.

### Open question

> We do not have enough evidence to answer that reliably yet. We would need the transaction-level exception data or a short validation with the finance owner.

## Common executive questions

Expect:

* Why has this problem survived if everyone knows about it?
* Why is AI needed here?
* Could we solve this with existing software?
* What happens if adoption is lower than expected?
* What is the implementation risk?
* What data do we need?
* What would you do first?
* How confident are you in the ROI?
* Who needs to own the change?

## Do not defend every recommendation

If new evidence shows a recommendation is weaker than you believed, change it. Credibility comes from the quality of the decision process, not from never revising your view.

## Keep answers concise

Answer the question first. Add detail only if requested. Senior rooms lose confidence when the consultant responds to a two-sentence question with a five-minute monologue.