Run enterprise discovery

Purpose and scope

Structure early conversations around outcomes, users, controls, capacity and integration before a tailored proposal is written.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• Business outcomes and current pain points.
• Expected users, locations and data volumes.
• Required controls, integrations and decision timetable.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For run enterprise discovery, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• A scoped discovery record.
• Assumptions and exclusions.
• A route to demonstration, pilot or proposal.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.