Learn by watching

icon picker
Coda in action

As you learned with and , you don’t need to reinvent the wheel with each doc. The set of videos below include best practices we’ve compiled from real-world doc scenarios. We challenge you to apply—and adapt—them to your own docs.

Company wiki

Build a company wiki, complete with an intuitive hierarchy, engaging styling, and interactive data.

Step 1: Structure

When it comes to doc structure, you’ll want to rely on pages. Here’s a look at how you can build a page hierarchy to create an intuitively organized wiki.

Step 2: Formatting

Use doc styling—from text size to colors—to communicate importance and invite engagement.

Step 3: Company calendar

In this video, you’ll see how to turn a company event tracker table into a calendar that keeps your team accountable.

Step 4: Org chart

Create a company roster that can be used in other docs in your Coda workspace.

OKR tracker

Track your company’s OKR progress while giving teams space to focus on their tasks—all in a single doc.

Step 1: Structure

Your OKR doc will have two main tables that tell the story of how your company’s goals fit together. Let’s get set up right!

Step 2: Team Views

Even thought it’s helpful to see the big picture, we also need to the ability to focus on just the OKRs for my team. In this video, we build views for each team to meet their needs.

Step 3: Escalation

Things don’t always go smoothly, and healthy teams flag issues before they become a major problem. This video walks through how to escalate and ask for help.

Step 4: Reflection

Setting OKRs is only part of the puzzle. Reflection and learning from performance is just as important. Here we close the loop so we can get better quarter after quarter.

Team task tracker

Your team deserves a single source of truth. Reduce redundant and inconsistent data by creating a team task tracker.

Step 1: Connect to OKRs

Tasks without goals end up being busy work, but no one wants to jump from tab to tab to find focus. Here we bring in all the great OKR work your company has done to add context to your tasks.

Step 2: Task Views

As we go through our day, we have different questions we need to answer and different parts of our data that matter. In this video, we build custom views of your tasks to support you in meetings and build focus.

Step 3: Dependencies

Tasks don’t exist in a vacuum, and sometimes order is important. Here we build in dependencies between your tasks to help you plan.

Step 4: Summary by People

Summarizing your data helps you notice trends and adjust your plan. It also makes checkpoints more efficient. Here we’ll summarize task progress by teammate.

Step 5: Automated Email Reminders

We could all use an assistant. Here, we use Coda and the Gmail pack to automate task reminders on our own terms.

Meeting structure

Design your meetings like you would an app—with consideration for audience and content.

Step 1: Before the Meeting

Preparation is the key to an effective meeting, but traditionally that can take a lot of time. Let’s explore how Coda can streamline the prep process to save you and your team time and improve meeting quality.

Step 2: During the Meeting

But, what about when we’re in the actual meeting? And what if some of us are remote? Not to worry. Coda’s got you covered with an easy note taking and tracking process. We’ve also got tips and tricks for a more inclusive conversation.

Step 3: After the Meeting

You’ve had your meeting, but now it’s time to get some work done, and make sure no action items fall through the cracks. Let’s build an effective close out process to promote transparency and productivity.

Check your progress.

Here’s a view of your learning plan. What do you want to accomplish next?
Time commitment
Watch the videos.
80 mins
Not Started
Subscribe to the Coda webinar channel at .
1 min
Not Started
Bookmark the links in .
1 min
Not Started
Begin .
Not Started
No results from filter
1 hr 22 mins
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.