Team hub with embeds

Explore

Meetings

Decision framework

A quick brief for requesting feedback async or during a meeting.

Make an informed decision quickly, while incorporating everyone’s feedback. Use this template to meet live, or seek feedback async and then determine if a meeting is needed. Adapted from

Two-way writeups: Coda’s secret to shipping fast⁠

⁠

Copy this template

⁠

to generate a fresh copy to fill out, nested under this page

After you’ve made a copy for an upcoming decision,

Clear sample data

⁠

Background

Since Coda’s inception, we’ve debated whether the toolbar should be fixed or inline. More recently, the inline toolbar was one of the features that we scoped out of the original visual refresh project. Our guiding principle behind the visual refresh was to minimize Coda UI and make more space for the user content to shine. In the same vein, the top toolbar is a piece of UI that permanently takes up real estate on the screen, even though it is not actually used that often. More importantly, the toolbar makes Coda docs feel more cluttered and “work in progress” for viewers and contributors. For that reason, we believe that switching to the inline toolbar will make Coda docs feel more lightweight for simple cases and more presentable for sharing with others.

⁠

Proposal

Launch the inline toolbar in Q2. This will involve cross-functional efforts across Product, Design and Brand teams.

Should we delay the launch?

Launch in Q2

Pros: launch will be part of holistic story with the other visual features scheduled for Q2.

Cons: less time to aggregate feedback from user research.

⁠

Launch in Q3

Pros: launching in Q3 allows more user testing and we can create more marketing assets.

Cons: launch will be separate from the other visual features scheduled for Q2.

⁠

Done reading?

⁠

Dory: questions & discussion topics

Add and upvote questions or discussion topics below.

Idea

Author

Answer

Upvote

Downvote

Since there were some dependencies on the Go-to-Market team, can you speak to the timing of your next phase of testing?

Open

Re: experimentation ー I’m confused by the wording, I understand that we’re aiming to understand impact through other methods, so is there a need for an experiment writeup?

Open

Thoughts on setting up a few one-liner canned responses to the potential “who moved my cheese” questions? Even if we don’t use them, it’s worth the exercise.

Open

Is it worth setting up a form/doc/community post/something else where users can submit anonymous feedback? (post-beta)

Open

There are no rows in this table

⁠

How do you feel about launching in Q2?

⁠

4

⁠

sentiments added.

Only show me

Pulse Check

Reflection

Author

Ship it in Q2! It’s a huge improvement and I think will really benefit power users and new makers alike. My only concern is it sometimes shows up when I don’t want it, but I think we’re balancing that fairly well on the whole.

Let’s get this feature out there ASAP! It’s made room for some delightful visual updates like transparency over cover photos. 👏 We can all align to ship fast.

I’m generally bullish on a faster launch. I think we can work together to make the launch successful, and we have headcount to ensure our other launches still occur on time. Let’s make sure we meet to walk through timeframes and remaining tasks.

I generally feel good about launching in Q2. I think there is strong appetite, and we have the resources to ship soon. If we align quickly, we should remain fully on track.

There are no rows in this table

⁠

Gallery

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.