#AIRTABLE ICON PLUS#
The culmination of those synced tables, plus the added layers above is what makes up the Product Tracker Zach uses today. The team, feedback, and OKR tables, for example, are pulled in as synced tables from separate bases. Not every level of the Product Tracker is captured natively within the Product Tracker. This helps link individuals to projects, and appropriately route feedback and notifications. Team: A detailed directory of who works at the org, including Slack handles, the team they roll up into, the product areas they’re responsible for, role, and more.Feedback: A repository of user feedback on specific projects and betas, as well as Airtable more broadly-used to route feedback to the corresponding product teams for consideration.Releases: Batched groups of functionalities and features shipping at one time, used to give customer-facing teams a preview of what’s next before it launches-and to keep them up-to-date on betas they can invite their customers to, and features to test internally.Updates: A centralized log of progress updates as the team moves through the development process, keeping the org informed as they get closer to shipping.Docs: Internal documentation on features in progress, like product requirements documents (PRDs), internal FAQs, plus external-facing support articles.OKRs: Top-level goals for the organization, used for planning, and to map projects to their respective goals.Projects: A log of all customer-facing features, plus back-end improvements to augment Airtable’s speed and capabilities (but aren’t directly visible to customers).To capture all of that critical detail, the Product Tracker is split into seven key levels: projects, objectives and key results (OKRs), docs, updates, releases, feedback, and team. > Get a closer look: learn more about Zach’s approach in this ebook The result is a dynamic, always-on source of reliable data for the rest of the organization to build off of. Zach’s base works to capture all of that information in one place, and enable product team members to share updates on their work within it. “There are a lot of moving pieces within a product organization-especially one that’s scaling rapidly,” Zach shared. The team calls it the Airtable Product Tracker. To build the foundation for Zach’s workflow, he first started by building a single source of truth: one Airtable app that encapsulates everything the product team is working on, who’s working on it, when it’s shipping, and more. At the end, you’ll find a step by step guide to building something similar for your team. Read on for a peek at how Zach built a living roadmap within Airtable-and how he uses that roadmap to power scaled communication and better visibility across the organization. So we wanted to ensure that product teams don’t have to repeat themselves, or share information in multiple places.”
“Teams get a lot of questions, especially with new folks coming on board every week.
“As our team has grown, we want to make sure our product org is able to communicate with the company at scale,” Zach shared.
One of the most challenging pieces of that puzzle is the product roadmap: keeping the team and their partners informed on what’s coming next.įor Zach, building a living roadmap was a start-but he knew they could take it even further. But as the team has scaled, so have the number of updates, teams, and stakeholders to keep track of-and that growth has added a new level of complexity to the team’s operating model. Learn how the team uses Airtable automations to manage roadmap communications at scale.Īs a founding member of Airtable’s product operations team, Zach Felsenstein helps bring new features to customers.
0 kommentar(er)
