diff --git a/content/copilot/how-tos/use-chat/use-chat-in-github.md b/content/copilot/how-tos/use-chat/use-chat-in-github.md index c9da69f3324f..0288ca0f065f 100644 --- a/content/copilot/how-tos/use-chat/use-chat-in-github.md +++ b/content/copilot/how-tos/use-chat/use-chat-in-github.md @@ -116,13 +116,11 @@ To navigate between subthreads: ## Powered by skills -{% data variables.product.prodname_copilot_short %} has access to a collection of skills to fetch data from {% data variables.product.github %}, which are dynamically selected based on the question you ask. You can tell which skill {% data variables.product.prodname_copilot_short %} used by clicking {% octicon "chevron-down" aria-label="the down arrow" %} to expand the status information in the chat window. - -![Screenshot of the {% data variables.product.prodname_copilot_short %} chat panel with the status information expanded and the skill that was used highlighted with an orange outline.](/assets/images/help/copilot/chat-show-skill.png) +{% data variables.product.prodname_copilot_short %} has access to a collection of skills to fetch data from {% data variables.product.github %}, which are dynamically selected based on the question you ask. You can explicitly ask {% data variables.copilot.copilot_chat_dotcom %} to use a particular skill - for example, `Use the Bing skill to find the latest GPT4 model from OpenAI`. -You can generate a list of currently available skills by asking {% data variables.product.prodname_copilot_short %}: `What skills are available?` +Generate a list of currently available skills by asking {% data variables.product.prodname_copilot_short %}: `What skills are available?` ## Asking {% data variables.copilot.copilot_chat_short %} questions in different contexts diff --git a/content/copilot/tutorials/roll-out-at-scale/enable-developers/drive-adoption.md b/content/copilot/tutorials/roll-out-at-scale/enable-developers/drive-adoption.md index b572a5bd0ff9..1aecfc974351 100644 --- a/content/copilot/tutorials/roll-out-at-scale/enable-developers/drive-adoption.md +++ b/content/copilot/tutorials/roll-out-at-scale/enable-developers/drive-adoption.md @@ -29,6 +29,16 @@ The {% data variables.product.prodname_copilot %} enablement process can be brok * {% data variables.product.prodname_copilot %} must be set up in your {% ifversion ghec %}enterprise and {% endif %}organization. For more information, see {% ifversion ghec %}[AUTOTITLE](/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise) and {% endif %}[AUTOTITLE](/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-organization). +## Example rollout timeline + +For optimal {% data variables.product.prodname_copilot_short %} adoption, tailor the timing and approach to your organization’s needs. For example, a rollout timeline might look like: + +1. Begin onboarding 45 days before rollout: define success metrics and train champions. +1. Share announcements and asynchronous resources 14 days out. +1. Host a workshop at 7 days out. +1. On launch day, provide a Slack channel, wiki, and curated online resources. +1. Continue to provide training. This can be formal at first, then shift to specific, on-demand support as adoption grows. + ## Granting licenses Before you can drive adoption of {% data variables.product.prodname_copilot %}, you need to ensure that your teams have access to the product. For more information, see [AUTOTITLE](/copilot/managing-copilot/managing-github-copilot-in-your-organization/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization). @@ -83,6 +93,27 @@ You can also use {% data variables.product.prodname_discussions %} to create a s {% data variables.product.github %} also provides a dedicated {% data variables.product.prodname_copilot_short %} Workshops repository, which contains a selection of workshops designed to help teams learn how to use {% data variables.product.prodname_copilot_short %} effectively. See [Copilot Workshops](https://github.com/copilot-workshops). +The following sections provide practical examples for helping teams to start using Copilot successfully, sourced from real organizations. + +#### 1. Run a team onboarding sprint + +* Set aside a day or week where everyone focuses on using Copilot. +* Pair up experienced developers with newer team members to explore Copilot in your real codebase. +* Encourage everyone to try Copilot for a specific workflow (such as writing tests or drafting content). +* Debrief as a group. What surprised you, what worked, and what didn’t? + +#### 2. Build regular feedback loops + +* Add Copilot discussion to your sprint retro or weekly sync. +* Prompt: “What’s one place Copilot helped (or didn’t) this week?” +* Use patterns from these conversations to tweak team documentation or onboarding. + +#### 3. Track and celebrate success + +* Pick a few metrics that matter (such as faster PRs or fewer “how do I start?” questions). +* Share wins in your team channel or during meetings. +* Recognize individuals who help others get value from Copilot. + ### Providing learning resources In addition to your onboarding resources, you may want to provide a library of learning resources to help teams advance their skills with {% data variables.product.prodname_copilot_short %}. The {% data variables.copilot.copilot_chat_short %} Cookbook is a great place to start. The Cookbook is a collection of example prompts that you can use to learn how to ask {% data variables.product.prodname_copilot_short %} for help with a wide range of tasks. See [AUTOTITLE](/copilot/copilot-chat-cookbook). @@ -101,3 +132,9 @@ Once you have implemented your {% data variables.product.prodname_copilot_short * Following up with users who haven't been using their assigned license. You can use the API to see the latest activity date for each assigned seat. See [AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/reminding-inactive-users). * Gathering feedback from teams to understand what is working well and what could be improved. * Reviewing {% data variables.product.prodname_discussions %} and other communication channels to identify common issues and questions. +* Iterating on your enablement process based on lessons learned. +* After a successful rollout, sharing your onboarding checklist or playbook with other teams to scale adoption. + +## Further reading + +For more concrete examples and a detailed playbook, see the [Training and Onboarding Developers on {% data variables.product.prodname_copilot %} whitepaper](https://github.com/resources/whitepapers/training-and-onboarding-developers-on-github-copilot).