Use Case Lifecycle
Once you've picked a use case to build, you'll want to take the following steps to maximize your chance of launching that use case to production.
Step 1: Understand the use case
A clear understanding of business requirements is essential before you start building. Creating mock-ups make the requirements explicit.
- Use our purple chat builder to create a mock-up.
- Ensure that mock-up follows all our mocking best practices .
Step 2: Derisk the use case
Every use case has 2 main risks.
- Conversation Design Risk: Make sure your developer understands how to use the appropriate combination of triggers, slots, actions, and guidelines to build the use case. This may require adjustments to your mock-up.
Pro tip
Our design patterns are popular examples of these combinations that your developers can follow to derisk the conversation design.
- System API Risk: Make sure the target business system has APIs that will allow your copilot to integrate with it. For example, if your system only has purchase order APIs, you can't build an invoicing use case.
Impossible Use Cases
It's possible that your use case may not be possible. If that's the case, don't worry, just pick a new one and restart the process.
Step 3: Build the use case
Once your use case is derisked, just keep the project on track. Always have a milestone with a target date and report on it regularly. You can follow our delivery schedule templates with a weekly stand-up if you need help with this process.
If you ever get stuck, feel free to setup a use case working session
Step 4: Test the use case
- Get access to any test / UAT business systems
- Identify testers and tell them how to use your use case
- Launch the use case to testers
- After a few days, get sign-off on the experience
Step 5: Launch the use case
- Get access to any production business systems
- Send launch communications to all relevant users about this use case
- Check back after day 1 & day 7 in analytics to make sure everything is working.