Feedback wanted: brand new template gallery w/ over 80 templates

As of several minutes ago, our brand spankin’ new template gallery shipped! We are really excited about it. Our previous gallery had around a dozen templates. This gallery was designed to make it easy and fun to browse through the 80+ templates we’ve built for it and… with your help, hundreds more.

Check it out

Two things I would ask from you:

  1. What do you think? Would love your feedback on the experience of browsing around as well as on the templates themselves — are they helpful? What templates would you like to see?

  2. We’ll be formalizing the process of submitting templates but if you are chomping at the bit we would love to hear about any potential templates you make. If you’ve got one feel free to use the “Submit your doc” button and send us the link (be sure to share it with support@coda.io so we can see it).

11 Likes

WOW. LOVE THIS!!!
I am having trouble scrolling to see the ones on the right (no scroll bar) but I can get to them with Ctrl - a few times.

1 Like

@jerols it is gorgeous!!! I didn’t opened all the templates yet, but I like the many choices you gave us.

1 Like

I like it. … and I like many of the suggestions in the gallery.

I ran into the same issue on horizontal scrolling until I finally noticed the “See All” link. Might emphasize that a bit.

I also didn’t think the Copy Doc was working. Maybe have it open directly into the doc. I eventually went back to my document list and found many copies. (Ah, just noticed that Chrome is blocking a pop-up here).

This is great! :grinning: I was able to find a bunch of awesome templates within minutes. My favs so far are the flashcard study guide and the habit tracker. I also love all the different options for to-do lists. Seeing everybody else’s makes me want to add my own.

I think it would be awesome if it was a bit more social. Even adding something as simple as the ability to “like” templates would make it easier to find good templates and a lot more rewarding to post templates. That would also make a “user’s choice” section of the front page possible :+1:

3 Likes

Look and feel of the gallery is well-designed compared to original gallery! +1 to @zoglow’s idea of a most-liked template by the crowd. A few things that would be interesting to add (if I put on my business hat):

  • The templates are categorized by task, I think a separate industry classification would be interesting (e.g. non-profit, real estate, education)

  • Within the industry categories, sanitized templates used by actual teams within these industries

4 Likes

Thanks!! Glad you like it.

Good point on the scrolling issue. We removed the scroll bar because it was a bit ugly to have so many of them. Do you have a mouse that scrolls horizontally? I’m thinking we could add some arrows for people who don’t have that.

cc @Brian_Eshelman

Great idea on making it more social. It’s something we couldn’t get into this version but definitely something we are thinking about.

1 Like

Now that I see the “see all”, I’m good. Maybe bold that or make a bit bigger.

I know I’m late, but I LOVE the templates section. It’s exactly what I needed in order to get my team on board easier (it is a lot harder to start them from 0). Thank you!

Hi @jerols,

I’m new to the community and recently read your post. While over a month since your request, offering my feedback in case it’s still helpful.

IMHO, hands down the best feature of the template gallery is the ability to demo before selecting a template. Instead of having to first create a new document, the user is provided a frictionless experience for determining whether a template meets the intended use case (i.e. try it, then save or discard). This is a superior approach!

Considering the templates themselves, the context for my feedback is as follows:

  • I limited my examination to the eleven templates in the Project Management category, thinking these would be germane to nearly all businesses.
  • While I’ve worked with many SMBs in my career, I tend to critique using an enterprise lens, assuming Coda’s GTM strategy will target organizations with more than a few hundred users.

There are a couple of templates that are creative gems, namely Meeting Timer and Simple Status Updates, which make the everyday tasks of running meetings and collecting status efficient and almost effortless. There is also good value to be found in the other templates, as well as some opportunities for improvement. Consider one example: Kanban project.

I realize a basic Kanban board has the three-step workflow you’re presenting, but the oversimplification and very thin sample data gave me the “slapped together” feeling. As the theme for the board is software development, in the next iteration you might consider expanding the swim lanes to include something like Develop, Test and Deploy. I also suggest creating a section at the top of the document to explain Kanban at a high level, and include a graphic representation of the physical Kanban card that you are modeling. Finally, since the goal of a Kanban system is to limit the amount of work in process so that work flowing through the system matches its capacity, demonstrating WIP limits through conditional formatting seems essential.

Stepping back to the forest view, I’m always more intrigued by templates which appear to contain real data. I’m not suggesting you expend the effort to create a fictional company à la MSFT’s Contoso (although you could evolve to something similar over time). Rather, since software development is a theme for many of these templates, a sanitization of a small portion of Coda’s own process steps and data would add a nice level of robustness.

I’ve saved the most important comment for last. This only applies if it is your intention to make Project Management a primary use case for Coda.

Collectively, the templates showcase powerful means of tracking and visualizing project status. In my experience, both as a program manager and working with others who are much smarter than I am, PMs and TPMs also need a method for measuring project velocity. For a software engineering project, measuring a team’s velocity is important to help understand what the team can build over a set period of time (e.g. a calendar quarter).

From my Google days, we used a bug tracking system to capture work for both resolving defects and building features. Since this is fairly standard practice, a TPM can use bugs fixed per time period as a proxy for velocity. Consider the illustration below, where the following three columns of data are imported once per week from a bug tracking system into a Coda table:

[# open P1 feature requests] [# open P1 defects] [# resolved P1 feature requests]

While this illustration is greatly simplified (e.g. a true velocity measurement would consider the size of each task), a weekly snapshot would enable a TPM to measure velocity over time and estimate a delivery date.

Apologies for this lengthy reply. Very much appreciate the team’s hard work and the opportunity to offer actionable feedback. Thank you!

2 Likes

@jerols The templates are a great basis to learn how certain challenges can be overcome

I would recommend to have a bidirectional links between the formulas used (or combination of) in each of the templates. This gives the users not that familiar with formulas an eye opener on the potential of Coda.

Looking forward what’s more to come…

Kind regards,
//JP

1 Like