[carliny]

Hey there! Tables PM here -- thanks for writing an honest opinion about what factors you're considering before wanting to use it for a business; I really appreciate that feedback and it's very helpful for us to hear.

I know our team would love to have people try Tables for lightweight work tracking use cases, even if it's not for a mission-critical business need. At the end of the day, we want Tables to help people and businesses make work a little easier, especially with covid forcing many to digitize and work remotely. If we're able to create a lot of value, that'll make for a strong case to graduate Tables into a larger Google product area, and we're only going to be able to do that with feedback from folks like yourself who can apply a healthy dose of objectivity. :)

Thanks for sharing your thoughts on this, and we hope you'll give Tables a little time (even Keep took several years before finally joining G Suite)! I'll also take that feedback on the "beta" label back to the team.

[crazygringo]

Well nice job carliny in launching it, well done! And good luck.

I could see a lot of small groups adopting this -- college extracurricular groups, a team at a church, friends organizing a short film -- and if you're focusing on usage metrics, that whole universe could prove to be far larger than the business market, at least before it's included in G Suite. Think of how many people use Forms+Sheets for that stuff right now.

However, my $0.02 would be that, right now, if I were one of those, I'd look at the landing page and assume that I'd quickly run into a limit and be tricked into paying $10/user/mo., so I'd avoid even trying it out. The 1,000-row limit seems like something I might easily run into, for example if I were simply importing all the alums from the organization's 30-year history.

I wonder if you couldn't come up with a better separation between free and paid that didn't depend on storage, but solely on features? For example, imagine if Sheets were free but charged if you wanted to use pivot tables and database connectors -- something like that. (Also, total storage is hard to estimate in advance, perhaps better to have a limit on attachments per-row? E.g. 64 KB, and it will automatically convert images to JPEG with lower quality/resolution as necessary? Otherwise everything is stored as a link to someone's Drive file?)

I just think if you communicated this as "100% free" but then with a "paid business integration add-on" or something, people would be a lot more willing to try it out. Again, best of luck!

[carliny]

Thanks, crazygringo! Appreciate the kind words.

Absolutely, we're really hoping that Tables can be great for all those smaller groups and use cases as well. The feedback on your impressions of the landing page is really helpful; I'll take that to the team and see if we can improve on that.

For some context on the tiers, I agree that storage is becoming a commodity and may not be something to gate on too heavily. For some quick insight, we did an analysis and the vast majority of lightweight work trackers (not for a serious business use case) had far below 1000 rows/records in them, so we left it with that limit to mitigate abuse, and then give 10x in the next tier (plus, we only charge for a single license, not by # of collaborators). That said, your point about making it easier for people to just jump in and get started is very valid. Thanks for giving me and the team some food for thought, we'll noodle on this and see how we can improve the messaging! :)

[Terretta]

How are you addressing business data compliance?

A kanban central like this essentially contains a snapshot of the company and its direction, “outside”.

RBAC w/ segregation of duties on the admin side and least privilege assurances, audit trails, SOC2, HIPAA, etc. etc... ?

[carliny]

Hey Terretta, great question. Tables is already built on standard Google infrastructure so we have many of the default security and privacy protections built in.

From a user-facing standpoint: Tables is really geared towards being more user-friendly than the traditional DBA type tools, so the sharing model aligns more closely with Google Drive, and offer similar permissioning roles like "Editor", "Commenter", and an additional "Writer" role for collaborators who should be able to edit the rows, but not the table schema itself. We also have table and row-level change history baked in, and while we don't specifically offer an audit trail within the app, users can implement a version of that themselves using our bots. We're also working to support the ability to use bots to essentially automate GDPR compliance, by having bots that will automatically delete table rows that are >X days old.

From a customer-to-Google standpoint: we are very serious about your data privacy and security. We're not currently rubberstamped for HIPAA/SOC2, but we're already in the process of going through the internal reviews for FEDRAMP and HIPAA compliance. We do not at this time have advanced enterprise admin controls for customers, but it's absolutely coming in the future (we are only 1-day old to the public :).

We're not going to have all the angles covered, but we're working towards it!

[dano]

When will Tables be added to G-Suite as a core product? Time frame? Gating factors?

Adopting a new workflow and project process is a massive investment in data conversion, adoption, training, and internal politics. For those reasons, my teams would need to know to a high degree of certainty that our efforts will be rewarded with a long term, well supported service.

Congrats on launching and I'll be watching to see how things go for this product.