Getting started & discovery
Choose a discovery service
Use the decision you need to make to select a starting scope, then check its listed deliverables before purchase.
Choose by the question, not the package name
The discovery store describes services with different amounts of working time and different written outputs. Read the current offer, duration and deliverables together. A leadership question, a focused workflow review and an architecture program need different preparation.
- Write the decision you want discovery to help you make.
- Compare the listed deliverables with that decision.
- Contact the team if the question spans more systems or stakeholders than the selected scope describes.
- Purchased hours describe the service capacity shown, not a guaranteed completion date.
- Implementation and ongoing operating support require a separate agreed scope.
Check fit before proceeding
The sample discovery report shows the form of the work. It is illustrative; it does not add deliverables to a purchased service. Preparation, participants, access requirements and scheduling are confirmed with the team.
- Check who needs to take part and who can approve the next decision.
- Note any provider access or records that may take time to obtain.
- Use the current store offer as the reference for price and scope.
If no listed service fits
Send the business question and the boundaries you already know. The team can discuss a suitable scope without treating a larger implementation as part of a small discovery purchase.
- The question and intended decision.
- The systems, teams or locations involved.
- Any timing constraint and its business reason.
Need help with your workspace?
Open a private support request with the steps, expected result and business impact. Leave out passwords, API keys and payment details.
Open client support