All Collections
Account Management
Team Collaboration
Best practices for team collaboration
Best practices for team collaboration

Explore tips that help you work better with your team in Chameleon

Tiago Mota avatar
Written by Tiago Mota
Updated over a week ago

As your team grows it's important to organize your efforts to enable teammates to contribute in a way that makes sense for your use cases and company goals.

Here are some tips and best practices to help you collaborate easier with your team in Chameleon.

Collaboration tips

Plan your efforts together

Stay on top of your product's needs and think about the use cases to tackle, the people to involve, the ways you'll track success, and what are the internal logistics of setting Experiences live.

πŸ‘‰ You can start simple, assess the impact of Chameleon vs. nothing, and optimize your Experiences to increase your engagement rate. Internally, plan your steps, and discuss success metrics, and timelines with your team. See more on what data Chameleon collects and how to leverage it best, from the Experience Analytics Overview.

Assign a Chameleon Champion

It's easier for teams to move with speed and optimize better when there's a person responsible on the team for managing in-app Experiences. This person should ensure new Experiences go live as expected, monitor how users engage with them, and generally ensure things run smoothly on your account.

πŸ‘‰ Ask someone who's aligned with your company goals and understands users' needs. It can be your CS or Growth Manager, or someone on the product team.

Train your team

Although you may start with a few folks who need to access your account, it's not uncommon to see other teams and departments start using Chameleon soon after it is introduced in a new company.

To enable teammates who want to contribute to product communication, marketing promotion, or user research, you can help train them on what's possible with Chameleon early on.

πŸ‘‰ You don't have to do it alone --point them to our 101 Course (created for new users), or share our interactive demos, or Recipes to spark ideas.

Define your internal processes

Depending on your team's needs and size, it's useful for everyone involved (as well as any new teammates joining down the line) to know:

  • who can create and publish Experiences

  • what is the process of requesting new Experiences

  • where you track all live Experiences, upcoming needs, archived (all paired with goals and their respective results, target audience, timeline)

  • how to name, tag, or describe in-apps, or audiences so that anyone can understand at a glance what is happening in your account

  • what's the dedicated channel/person to go with questions/needs for in-app Experiences; you can also have a dedicated person that signs off any final details, such as copy, targeting, and sets Experiences live.

πŸ‘‰ We suggest you set at least, a basic set of naming conventions and guidelines around targeting, how long Experiences should stay live, and individuals responsible for creating and managing Experiences on your account.

Review performance regularly

You should regularly review your live Experiences to understand how your effort drives impact. Check your "Engagement Index" to quickly understand how users find your in-apps. When they lack engagement, you have opportunities to improve your triggers and segmentation. When things go well, you can uncover new ways to engage users.

πŸ‘‰ Every quarter you can look at your strategy and note where Chameleon has been most impactful in driving your goals; it's a good moment to incorporate other requests from your team and plan to tackle new use cases.

Chameleon best practices

Leverage Templates for a built-in style

The safest way to have any in-app look right out of your brand book is to leverage Templates so anyone creating a new Experience will have to focus on the message alone. Ask your designers to help polish the look and encourage your team to create new Templates when needed.

Enable MFA and optionally, SSO

Never worry about unauthorized access and ensure all your teammates can safely access your account. You can enable multi-factor authentication, or check out our SSO add-on available for any plan.

Use Roles for more control

If you need to balance access with permissions in your account, you can assign teammates as "Designers", "Publishers", or "Viewers" (Roles vary by plan). Each Role comes with assigned permissions across your account, so you can confidently invite your whole team to join without fearing disruptions when it comes to the user experience.

Use Tags to visibly keep track of efforts

Use Experience Tags to label different teams, efforts, use cases, or cycles. You can keep your account organized and anyone landing there will be able to find, track, or understand what Experiences are working or where priorities lie.

Set an unpublish date

When going live with your Tours and Microsurveys, you can also pick the date that they should stop displaying to your users. Getting into the habit of setting an unpublish date (especially for temporary campaigns) will save you time and ensure your users will never engage with out-of-date content. You can set internal best practices around how long different types of Experiences should live.

πŸ‘‰ It's also easier to keep track of recurring efforts, or in-apps that need constant updating. Just set the unpublish date and know that when you get the email notification from Chameleon, it's time to go in and update your Experience.

Success tips

Define your goals

The first step to achieving success is to define a simple, trackable, goal for your in-app Experiences. You may start from broad use cases like improving onboarding or deflecting support tickets, but you should get more specific when defining your goals to ensure they are achievable and easy to assess.

Know your users

Understand the needs and approach that your users respond to and try to create a pleasant experience for them. This applies to your segmentation, the way you trigger Experiences, as well as your content.

πŸ‘‰ Use everything you have at your disposal to learn about their experience and how to improve it (direct feedback, Hotjar recordings, collected data, etc.) If you're still unsure, just ask them directly.

Always collect feedback

Talk to your customers, especially once you start using in-app Experiences to understand how useful they are for them, or what's missing. You can use Microsurveys to uncover sentiment, challenges, or favorite features. Leverage AI summaries or response filtering to skim through responses and find opportunities.

Don't block users

With any in-app you create, keep in mind what other goals users might have at that moment. It's a good idea to allow them to snooze a Tour, or offer multiple (button) choices. For the most non-intrusive guidance, leverage Banners to allow users to engage when ready or interested.

Did this answer your question?