​
Rollout Process

​
0. Planning the rollout

After securing leadership buy-in, the AI owner and team plan the rollout. Before starting, create a rough plan of measures and initiatives to educate users. We recommend preparing these items:
  • Add your logo, security hints, and custom links to the platform
  • Set up SSO
  • Fill the prompt library and assistant library with suitable use cases
  • Set up a shared channel with your users and the Langdock team
  • Plan upcoming meetings and invite your users
  • Choose pilot participants

​
1. Exploration and first use cases

Now you can onboard users to the platform. This moment creates momentum and excitement that you should use to organically adopt the tool and find use cases. Week 1: Kickoff (45-60 min)
  • Initial meeting to get to know the Langdock team and platform
  • Q&A and understand next steps
  • First 1-2 company-specific use cases
  • Users are added to a shared Slack/Teams channel
Week 3: Deep Dive - Prompt Engineering (45-60 min)
  • Input from the Langdock team about prompt engineering
  • 1-2 company-specific use cases from users
  • Q&A and sharing learnings
Week 5: Deep Dive - How to build an assistant (45-60 min)
  • Input from the Langdock team about assistants
  • 1-2 company-specific use cases from users
  • Q&A and sharing learnings
Week 7: How to find use cases (45-60 min)
  • Input from the Langdock team about finding use cases
  • 1-2 company-specific use cases from users
  • Q&A and sharing learnings
  • Goal: Get people on board who haven’t found their use case yet
The Langdock team is available for 1:1 sessions for individual questions, ideas, and building use cases together.
The largest leverage for internal usage is building and sharing use cases with your user base. Share in the shared channel, check-ins, meetings, and company events to increase momentum and let users learn from each other.
At this point, you’ll have champions - ideally 1-2 in each department. They’re excited about AI, know how to prompt, and can build use cases. They’ll educate and excite others. Keep momentum by maintaining regular exchange and diving into attractive use cases.

​
3. Building out more use cases

After the first phase, onboard more users and build more use cases. The more AI champions you have, the easier this phase becomes. You will have some examples already, but should also encourage users to find their use cases organically. Below is a framework to do this. You can find more details here. Group Session - Defining Use Cases (45-60 min)
  • Collect 5 tasks that are repetitive and time-consuming
  • Prioritize based on impact and feasibility
  • Get started with 1-2 individual use cases
Group Session - Check-In after 1-2 weeks (45-60 min)
  • Share learnings
  • Check on use cases: What worked, what didn’t work, how did users build them?
Everyone finds use cases that would help in daily work. After the session, everyone experiments and tries to build use cases. Check in with users during this phase. After 1-2 weeks, meet again to share learnings.

​
4. Grow sustainably

Over time, users will organically build assistants, share prompts, and use Langdock more. Continue workshops, help users individually, and maintain AI momentum. You can slowly integrate other tools and work on higher-effort tasks:
  • Search integrations to read information from other tools
  • Assistant actions to read, update, and create data in other tools
  • Using the API to access Langdock from other tools
  • Agents for building highly individualized workflows

​
General measures

You don’t need to implement all these initiatives, but some might help maintain momentum:
  • Hackathons or Promptathons - Teams of 4-5 people work on problems using AI solutions
  • 30-day AI challenge - One small AI task daily to learn and build habits
  • AI newsletter - Share current developments, internal success stories, and tips
  • Reminder notes - Sticky notes saying “Use Langdock” to prompt daily AI thinking
  • Knowledge sharing - Share small tricks 1-2 times weekly (max 2 sentences)

​
Signs of a successful rollout

  • People are sharing use cases and learnings
  • Many people book 1:1 sessions
  • Users have questions in check-ins
  • Users create pull - they want more content and proactively build use cases
  • Successes are celebrated to maintain momentum
  • Leadership communicates clear goals and motivation
  • Good KPIs: Growing active users and increasing prompts sent

​
What to avoid

  • Don’t build many use cases at once - Focus on 1-2 first and adopt them properly
  • Don’t overengineer the rollout - Start simple, see what works, then adapt
If you have questions, want rollout support, or need a quote, reach out to support@langdock.com.