Team Collaboration Best Practices

Make the most of Zenovay as a team. Best practices for collaboration, workflows, and getting value from your analytics together.

Setting Up for Success

Team Structure

Recommended team setup:

Role	Who	Zenovay Role
Analytics Lead	Data/Marketing lead	Admin
Power Users	Active analysts	Editor
Stakeholders	Executives, managers	Viewer
Technical	Dev team	Editor or Admin

Access Philosophy

Start restrictive, expand as needed:

Default to Viewer access
Promote based on need
Review quarterly
Document decisions

Workflows

Daily Analytics Check

For marketing teams:

Morning Check (5 min)
├── View yesterday's traffic
├── Check goal completions
├── Note any anomalies
└── Share insights in Slack

Weekly Deep Dive (30 min)
├── Review week trends
├── Analyze top sources
├── Check funnel performance
└── Document findings

Goal Management

Coordinate goal creation:

Practice	Benefit
One owner per goal	Clear accountability
Naming convention	Easy to find
Regular review	Keep relevant
Document purpose	Context for team

Suggested Naming Convention

[Team]-[Type]-[Description]

Examples:
MKT-Lead-Newsletter-Signup
PROD-Activation-Trial-Start
SALES-Demo-Request-Form
ENG-Error-Rate-Threshold

Communication

When you discover something:

Screenshot or export the data
Add context - what, why it matters
Share in team channel - Slack, email
Tag relevant people - who needs to know

Insight Template

📊 Analytics Insight

What: Traffic from LinkedIn up 45% this week
Why It Matters: New campaign launched Tuesday
Data: [screenshot or link]
Action: Continue campaign, increase budget?

Regular Reports

Schedule automated reports:

Report	Audience	Frequency
Executive Summary	Leadership	Weekly
Marketing Metrics	Marketing team	Daily
Product Analytics	Product team	Weekly
Technical Health	Engineering	Weekly

Using Dashboards Together

Shared Views

Scale Plan

Create views for different needs:

View	Purpose	Who Uses
Executive	KPIs only	Leadership
Marketing	Campaign focus	Marketing
Product	User behavior	Product
Operations	Site health	DevOps

Dashboard Etiquette

Best practices:

Don't modify shared filters
Create personal views for exploration
Document changes you make
Notify team of new views

Goal Ownership

Assign Owners

Each goal should have an owner:

Goal: Newsletter Signup
Owner: sarah@company.com
Purpose: Track email list growth
Alert: Yes, when drops &gt;20%
Review: Monthly

Owner Responsibilities

Goal owners should:

Monitor performance
Investigate anomalies
Update settings as needed
Report to stakeholders

Troubleshooting as a Team

When Data Looks Wrong

Standard checklist:

Verify timeframe - Same dates?
Check filters - Any applied?
Compare sources - Match other tools?
Review tracking - Code deployed?
Escalate - Still wrong? Contact admin

Incident Response

When tracking breaks:

Step	Owner	Action
1	Discoverer	Report in #analytics
2	Technical	Investigate code
3	Admin	Check Zenovay status
4	Lead	Communicate to team
5	All	Document resolution

Training New Members

Onboarding Checklist

For new team members:

Account created and invitation accepted
Role assigned appropriately
Walked through key dashboards
Introduced to goals they'll monitor
Shown how to create basic reports
Connected to team communication channel
Given this best practices guide

Self-Service Resources

Point new members to:

This help center
Team documentation
Key dashboard views
Common reports

Documentation

What to Document

Keep records of:

Item	Where	Why
Goal definitions	Wiki/Notion	Context
Naming conventions	Wiki	Consistency
Access policies	Wiki	Security
Key metrics	Wiki	Alignment
Troubleshooting	Wiki	Efficiency

Goal Documentation Template

## Goal: Newsletter Signup

**Purpose:** Track email list growth from website

**Definition:** Form submission on /newsletter page

**Owner:** Sarah (sarah@company.com)

**Target:** 500/month

**Used By:** Marketing team, weekly reports

**Notes:** Excludes existing subscribers

Meetings

Analytics Review Meeting

Weekly team sync:

Analytics Sync (30 min)

Agenda:
1. Key metrics review (10 min)
2. Insights from the week (10 min)
3. Upcoming experiments (5 min)
4. Questions/blockers (5 min)

Attendees: Analytics team + stakeholders
Output: Action items in shared doc

Async Updates

Not everything needs a meeting:

Update Type	Medium
Quick insight	Slack message
Weekly summary	Automated report
Deep analysis	Written doc + discussion
Urgent issue	Immediate Slack/call

Common Pitfalls

Avoid These

Pitfall	Better Approach
Too many admins	Use Viewer/Editor more
No goal ownership	Assign every goal
Siloed insights	Share discoveries
Ignored alerts	Review alert relevance
Outdated goals	Regular cleanup

Signs of Good Collaboration

You're doing well if:

Team checks analytics regularly
Insights get shared and discussed
Goals are current and owned
Access is appropriate and reviewed
Documentation exists and is current

Tool Integrations

Connect to Your Stack

Integrate Zenovay with:

Tool	Purpose
Slack	Alert notifications, quick sharing
Email	Scheduled reports
Data warehouse	Advanced analysis
BI tools	Custom dashboards

Slack Integration

Set up Slack for:

Goal completion alerts
Daily/weekly summaries
Anomaly notifications
Team @mentions

Security Hygiene

Team Security Practices

Practice	Frequency
Review member list	Monthly
Check role assignments	Quarterly
Rotate API keys	Annually
Audit log review	Monthly
Remove departed members	Immediately

Access Reviews

Questions to ask:

Does everyone still need access?
Are roles still appropriate?
Any external members to remove?
Are API keys still needed?

Scaling Your Team

As Team Grows

Team Size	Considerations
2-5	Everyone can see everything
5-15	Consider role separation
15-50	Use website restrictions
50+	Consider multiple orgs

Advanced Features