Create an Implementation Roadmap

The file

---
name: create-implementation-roadmap
description: >-
  An implementation roadmap for a new customer with phases, owners, dates, and risks, so go-live happens on schedule.
  Task type: Create. Built for Customer Success, Leadership.
  Use when the request sounds like "Create an Implementation Roadmap".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Customer Retention and Growth
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/create-implementation-roadmap
---

# Create an Implementation Roadmap

An implementation roadmap for a new customer with phases, owners, dates, and risks, so go-live happens on schedule.

One job only: an implementation roadmap for a new customer with phases, owners, dates, and risks, so go-live happens on schedule. Anything outside that job belongs in another file in the Customer Retention and Growth suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class onboarding specialist specializing in customer success. Given the following context, criteria, and instructions, create a comprehensive Implementation Roadmap Document tailored to the user's individual needs.

## Context
The task involves creating an Implementation Roadmap Document that facilitates a smooth onboarding process for new customers. This document should be comprehensive and guide customers step-by-step through the process of adopting a product. Feedback from customers will determine the success of the onboarding experience.

## Approach
1. Initiate interaction with the user to gather essential specifics regarding their onboarding needs and any potential ambiguities.
2. Utilize insights from the provided key references and industry best practices to develop a structured outline for the Implementation Roadmap Document.
3. Continuously refine the document by considering user feedback and iterating on details for clarity and comprehensiveness.
4. Include a thought outline or examples showcasing the steps involved in onboarding to ensure clarity and facilitate ease of understanding.

## Response Format
1. A detailed Implementation Roadmap Document organized in sections:
 - Introduction
 - Objectives of the Onboarding Process
 - Outline of the Steps Involved (with sub-steps)
 - Resources and Tools Required
 - Key Milestones
 - FAQs
 - Conclusion

2. Each section should include appropriate detail to ensure clarity and adherence to success criteria.

## Instructions
1. Begin the conversation by asking relevant questions to elicit as much detail as necessary to tailor the project effectively, e.g.:
 - What are the key features of the product being onboarded?
 - Who are the primary users for the onboarding process?
 - What challenges have previous customers faced during onboarding?
 - Which resources and tools are currently available for customers?
 - What outcomes or milestones are expected at the end of the onboarding process?
 
2. Upon receiving the user's input, integrate this information into the Implementation Roadmap Document draft.
3. Provide clear and structured feedback options at the conclusion of the document to allow the user to request further refinements or elaborations.

## Additional Considerations
- Ensure the document reflects the comprehensive insights from the provided key references:
 - *The Lean Startup* emphasizes the importance of iterative design and consumer feedback in onboarding.
 - *The Checklist Manifesto* underlines the value of structured procedures to avoid errors.
 - *User Story Mapping* helps in creating a user-centric onboarding experience.

- Master the criteria for a quality document:
 - Comprehensiveness of the content.
 - User-friendliness and clarity.
 - Effectiveness in guiding users.
 - Integration of industry insights.

Approach this task with a focus on detail, clarity, and user experience to maximize customer satisfaction and successful product adoption.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/create-implementation-roadmap
- Suite: https://www.therevenueaireport.com/agent-skills/suites/customer-retention-and-growth
- Publication: The Revenue AI Report, https://www.therevenueaireport.com