Gallery
Share
Explore

icon picker
Weekly team meeting with Coda AI

verified-account

Keep everyone informed and on track.

Help your team stay in sync and keep cross-functional partners in the loop.
Drive accountability and action from meetings.
Take the work out of collaborating with other teams.
Automate discovery of key themes.
⁠
Delete sample data
⁠
⁠

Meeting summary

The team discussed new image editor development, including the possibility of accelerating the development process and conducting user testing. They also talked about planning a team offsite, creating a workback plan for next year's event, sharing customer stories, and onboarding a new engineer.
⁠
Send summary to Slack
⁠
Refresh meeting summary
⁠
⁠

Agenda

Covered?
Search
Covered?
Topic
Notes
Upvote
Added by
AI-generated action items
1
New image editor development
8
Lola Tseudonym
Susan to coordinate with Amy on HR for hiring process
Adam to check with team on QC and testing
Lola to reach out to sales team for beta customers and customers team for nominations on who to interview
Team to focus on making the editor easy to use and user-friendly
Team to consider creating comprehensive user guide and documentation, potentially in product tours, for the launch timeframes
Buck's suggestion of Q3 as the target date for shipping the editor to be considered for the large campaign planned by the marketing team.
2
Team offsite
4
Polly Rose
Check calendars for mid-June availability
Fill out survey for desired date options
Consider activities for offsite (painting class, city tour, botanical gardens)
Keep in mind: deadline for next launch, meeting with Denver-based customers, company holidays, and summer vacations
Plan fun icebreakers and structured team meeting time
Confirm budget with People team.
3
Share & discuss customer stories
2
Lola Tseudonym
Share customer stories page
Share examples from competitor promos
Decide on the best channels to share the stories as a team
Engage with the sales team and customer success team to conduct more customer calls to pull more customer stories.
4
New hire onboarding
2
Buck Dubois
Polly to make a list of people the new engineer should meet with.
There are no rows in this table
⁠
⁠

Cross-functional collaboration

What do my partners on other teams need to know?

Customers Team

The team should nominate beta customers for testing the new image editor.
The team should also consider recommending users to interview for the development process.

Design Team

The team should focus on designing new features, landing pages, or marketing assets for the new image editor.

People Team

The team should welcome and conduct onboarding sessions for the new engineer starting next week.

Product Team

The team should develop new features and products, specifically the new image editor.

Marketing Team

The team should prepare for a large campaign in Q3 to make the launch well-known across current and new customers.
The team should also share customer stories and examples from competitor promos, and decide on the channels to use for sharing stories.
⁠
Teams
Team
Responsibilities
1
Customers
Consists of sales, customer success, support teams
2
Design team
Designing new features, landing pages, or marketing assets
3
People
Recruiting, hiring, onboarding, planning company events
4
Product team
Developing new features and products
5
Marketing team
New campaigns, assets for new features and to raise product awareness
There are no rows in this table
⁠

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.