What should you do if the Discovery phase uncovers a previously unknown infrastructure weakness?

Question

Options

• AUse this new information to convince business executives they need outside resource to help
• BBrief the IT leaders on your findings,and gain agreement on how results should be presented to
• CKeep the information out of your Discovery report,so this does not cause a problem for moving
• DPropose a new,for-fee project to dig into the root cause of the problem.Put the

• A
  3% (1)
• B
  76% (26)
• C
  15% (5)
• D
  6% (2)

Explanation

Option B is correct because when you discover an unknown infrastructure weakness during the Discovery phase, the professional and ethical obligation is to brief IT leaders immediately, then collaboratively determine how findings should be communicated - this ensures transparency, maintains trust, and keeps the engagement moving forward with stakeholder alignment.

• A is wrong because using a vulnerability to sell additional resources is manipulative and self-serving; it exploits the client's concern rather than serving their best interest.
• C is wrong because omitting known risks from a Discovery report is dishonest and potentially harmful - it defeats the entire purpose of the Discovery phase, which is to surface the true state of the environment.
• D is wrong because immediately pitching a paid follow-on project before the current engagement is complete puts revenue ahead of the client relationship and looks opportunistic.

Memory tip: Think "Brief Before Billing" - always inform the appropriate stakeholders of what you found before deciding what to do about it commercially. Discovery findings belong to the client first, not the sales pipeline.

No community discussion yet for this question.