Skip to main content
Namita_Krishnan
Adobe Employee
Adobe Employee
August 25, 2026

New to Coworker? Five things to try in your first fifteen minutes

  • August 25, 2026
  • 0 replies
  • 45 views

If you have just gotten access to Adobe CX Enterprise Coworker, one of the first questions is usually: where do I start? 

Rather than trying to come up with the perfect prompt, I would spend 15 minutes experimenting with a few different parts of Coworker. The goal isn’t to get something huge done right away. It’s to get a feel for what Coworker knows, how it works, and where it can actually help with the work you do. 

Here are five things I would try. 

 

1. Ask Coworker what it can do for you 

Start with: “What can you help me do with the Adobe applications and capabilities available to me?” 

This is an easy way to get oriented without first having to figure out which product, feature, skill, or prompt you are supposed to use. You’ll get a much better sense of the range of things you can ask Coworker to do. 

 

2. Ask about something you work with 

Next, pick something from your day-to-day work and ask about it. 

For example: 

  • “Find the audiences related to [loyalty program] and summarize how they differ.” 

  • “What can you tell me about [specific journey] and its recent performance?” 

  • “Help me understand what’s happening with [specific campaign or audience].” 

Then follow up. If something looks interesting, ask: 

  • “Why do you think that happened?” 

  • “Can you investigate that further?” 

  • “What should I look at next?” 

This is where things start to feel different from a basic search or chatbot. Instead of hunting down different objects and pulling the context together yourself, you’re asking Coworker to help you make sense of the environment you already work in. 

 

3. Give Coworker a problem, not just a question 

This is probably the biggest mindset shift I’d encourage. Instead of spelling out every step, give Coworker a problem to work through. 

Try: 

“Our conversion rate for [campaign] dropped last week. Help me investigate what changed, identify likely drivers, and tell me what I should look at next.” 

You’re giving Coworker an outcome rather than prescribing every step. 

As it works through the request, try adding information or changing the focus: 

  • “Also compare this against the previous four weeks.” 
  • “Focus on the loyalty segment first.” 
  • “Exclude the period when the campaign was paused.” 

Real work rarely starts with a perfectly defined prompt. Requirements change. New information comes up. You realize you want to look at something else. 

You don’t need to write one massive prompt that anticipates everything. Start with the goal, see where it goes, and steer from there. 

 

4. See what skills and integrations you already have 

Before creating anything yourself, find out what’s already available. 

Ask: 

“What skills and integrations are available to me, and what can they help me do?” 

You can also narrow the question: 

“What skills and integrations could help me investigate campaign performance?” 

Skills provide reusable instructions for particular types of work. Integrations connect Coworker to the systems and information available in your environment. Pick one you haven’t tried and explore it. This can help you avoid rebuilding something that already exists and may give you ideas for capabilities your organization could add later. 

 

5. Teach Coworker one thing about how your organization works 

For the last few minutes, pick a process your team does over and over. It might be a campaign QA checklist, a standard performance investigation, a journey review, a troubleshooting procedure, or an SOP. 

Try: 

“Help me create a skill for our campaign QA process. Ask me questions about the steps, business rules, checks, exceptions, and expected output.” 

If you already have the procedure documented, try: 

“Help me turn this procedure into a reusable skill. Before creating it, identify any instructions that are ambiguous, contradictory, or missing.” 

You don’t need to finish the skill in your first 15 minutes. The goal is to understand the difference between asking Coworker to complete a task and teaching Coworker how your organization wants that type of work done. 

----------------- 

For experienced Coworker users: what would you tell someone to try in their first 15 minutes? Share a prompt, skill, integration, or technique that has helped you get more from Coworker. 

And if you’re new, use the comments to share what you discover or where you get stuck.