Lauryn Isford
Former Head of Growth at Airtable, previously product growth lead at Facebook
Where to hear and read about Lauryn Isford1 episode or test
Lauryn Isford is a growth leader who was head of growth at Airtable and earlier a product growth lead at Facebook, working on its growth in India. The lesson most worth taking is to build onboarding, metrics and pricing around what users need, not what the business wants from them.
experiment when you need to and to primarily see it as a risk mitigation tactic
Mastering onboarding | Lauryn Isford (Head of Growth at Airtable)
Lauryn Isford: the story and the lessons
1How Lauryn Isford rebuilt Airtable onboarding and lifted activation 20%
Isford has run growth in consumer social, e-commerce and B2B software. She was most recently head of growth at Airtable, was a product growth lead at Facebook working on its growth in India, and earlier led growth for Blue Bottle's e-commerce business.
Onboarding is her favorite subject and the one she knows best.
Airtable's rebuild was a portfolio of three projects, not one big redesign. The pieces were guided onboarding, personalization and ongoing education, plus retiring many tooltips and making smaller optimizations. Together they lifted activation 20% over about six to eight months.
An activation team spent 12 to 18 months on the overall rebuild. She says to celebrate any clear, statistically significant activation gain.
A guided wizard with a live preview was the most impactful change. It asks short questions, such as what kind of project you are building and what you want to track, using big easy buttons. The left half of the screen takes input while the workflow assembles on the right.
Users found building basic scaffolding too much work and needed guard rails. She is not sure the tooltip is dead, and thinks the wizard fits products with high cognitive load.
Isford shipped one generic flow first, then personalized. The team judged that a single flow served over 90 percent of needs. Personalization came only after the generic version worked.
Research on real behavior showed user clusters, such as a technical user with database experience versus someone trying a colleague's tool.
She segments by learning and building style, not job role. Buckets like visual learner versus data-forward builder beat classic segments such as marketing, product or operations. A research team defined the types outside production, and sign-up questions route each person.
A teammate invited only to update a sprint needs a very different onboarding from a builder. She says there is a lot of low-hanging fruit in personalizing onboarding.
Isford keeps advanced features off day one. Someone who has never built a workflow does not need automations yet. The team split necessary education from ongoing education, and the pop-up tips called 'the mole' move users from beginner to intermediate to advanced.
She credits the lift to hours spent with customers before designing. What a user needs to be onboarded well differs from what the business wants them onboarded to, and she says to keep the two separate.
2Lauryn Isford on activation metrics and North Stars
Isford prefers a hard activation metric that few users reach. Airtable used week-four multi-user: more than one person on a team active and contributing to a workflow in the fourth week. She likes metrics that 5 to 15 percent of users hit over ones that 40 percent hit.
If 40 percent are active at week four, only a fraction remain at months 12, 18 and 24. Lifting a 5 percent group to 6 or 7 percent would have large downstream effects.
She splits the metric into components before building anything. Airtable asked how many sign up as a team versus an individual, and how many reach week four. It compared people invited, ever active and active in week four, and defined what counts as active.
This work came right before the onboarding rebuild and showed where the biggest levers were.
Companion metrics stopped lopsided wins. Airtable added individual week-four retention and Build, a sophistication score, beside team activation. Some treatments made users more sophisticated without inviting teammates, and others kept people around without better building.
She says "this group of metrics actually really set us free".
Isford adds guardrail metrics next to every North Star. A North Star lets a team focus on one result, while guardrails catch wins that hurt the business. An onboarding win that causes a 10% revenue drop is her example.
When a guardrail drops, the team should dig into which part of the onboarding caused it. Analysts, PMs, engineers and designers all share that rigor.
She holds a North Star for six months, then changes it on purpose. Stability builds momentum, domain expertise and compounding impact. After that, a metric that feels like old news may mean the team has outgrown it.
She starts by drawing the funnel on a whiteboard, and says the metric should measure whether the strategy is delivering, not dictate the strategy.
Airtable moved its growth North Star from revenue to user growth. Chasing revenue led to short-term decisions. The team took a decades-long view, since users could be converted to paying customers later.
In product-led sales the goal is often a handoff to sales for an Enterprise contract, so delaying revenue can make sense. Changing a North Star is a big deal because it ripples through several teams.
3Why Isford argues teams over-experiment
She treats A/B tests as risk mitigation, not a default. Every test costs engineers, analysts and PMs time that could go to roadmapping, foundational analysis or shipping. Measuring activation at 6% versus 7% adds little beyond a line in a performance review.
Her alternative is more time with customers, a sharper problem definition and mocks shown to people, so the team ships with conviction.
Airtable shipped a form-copy feature with no A/B test. People who fill in an Airtable form had no way to keep a copy of their answers. The team added one, gated on creating an account, because customer analysis showed demand.
They accepted that signup rate or activation mix might shift, and used attribution to analyze the effect after launch. Her example is wanting a copy of the T-shirt size you emailed for a swag order.
Isford says leaders must reward impact that is not a metric lift. If engineers must point to numbers to prove their impact, the team will bias toward experimenting on everything, which she calls a very expensive cost for the business.
Qualitative feedback, deals closed and deals not lost can show a team did right by customers. It works best when the head of growth sets the tone, and it cannot excuse sloppy building or vague customer needs.
4Isford on teaching features and designing pricing paths
She avoids naming features in tooltips. A tooltip saying 'this is automations' announces the feature and leaves a new user unsure it fits, or even what the word means.
She says "try not to name features it can be very tempting in practice even though it sounds easy in theory". Better is a one-touch turn-on or setting up the automation to finish the user's workflow.
Isford refuses to build onboarding around the pricing scheme. Pushing a premium feature like automations early is tempting when users of it often pay. It does not help a new user get started.
She roots onboarding in the customer's need and maximum value, not the packaging or the company's interest.
She favors a reverse trial: a free plan plus a premium trial. A trial of 7, 14 or 30 days shows everything the product can do, then users fall back to free. It adds paid conversion on top of user growth and brand awareness.
The choice should follow how the company wants to monetize, and she suggests stepping back from competitors' pricing pages. A free plan for tens of millions of people values user base and brand over revenue.
She gives sales-led products a way to show value with no human present. Options include a sandbox or demo, custom landing pages, and sign-ups that lead to education before any option to pay.
When a Fortune 500 customer already has a contract, someone signing up from the same email domain can get an experience built for contracted organizations, which grows the account.
5Isford's PLG funnel, growth team design and hiring
She frames PLG growth as join, evaluate, upgrade, expand. Join is signing up, evaluate is seeing the product will deliver value, upgrade is converting by card or sales, and expand is adoption spreading through the organization.
She chose 'evaluate' over 'onboard' or 'activate' because it is about what users need to see. Expansion drives net dollar retention and renewals, and feeds referrals back into join.
Isford uses the funnel as shared language, not as four KPIs. A team can explain why it invests in landing pages for join over onboarding for evaluate, and revisit the choice over time.
She says it should not map exactly to team structure or to four metrics.
Airtable's growth teams followed the funnel, with expand added later. Acquisition owned join, activation sat closest to evaluate, and monetization owned pricing and upgrade, plus churn prevention, downgrades and some billing projects.
An expand team came only once larger companies were using the product. She calls it an example of revisiting priors and staying agile in org structure.
She says B2B growth needs far more customer contact than consumer growth. With fewer customers and concentrated revenue, high-volume experiments are not available and a few customers can be a large share of revenue.
She leans on customer conversations, beta tests, live prototypes and demos. She says "face time with the customer is significantly more important than it is in b2c".
Isford hires growth people for intrinsic drive to have impact. Her interview question is to describe a time they delivered something impactful, and she listens for how the person defines impact.
She gives new reports Bob Iger's The Ride of a Lifetime.
Mastering onboarding | Lauryn Isford (Head of Growth at Airtable)
Lauryn Isford explains how Airtable rebuilt onboarding around a guided wizard, a stricter activation metric and a clear PLG funnel. The work produced a 20% lift in activation rate over about six to eight months.
Isford has run growth in consumer social, e-commerce and B2B software. She was most recently head of growth at Airtable, was a product growth lead at Facebook working on its growth in India, and earlier led growth for Blue Bottle's e-commerce business.
Onboarding is her favorite subject and the one she knows best.
Airtable's rebuild was a portfolio of three projects, not one big redesign. The pieces were guided onboarding, personalization and ongoing education, plus retiring many tooltips and making smaller optimizations. Together they lifted activation 20% over about six to eight months.
An activation team spent 12 to 18 months on the overall rebuild. She says to celebrate any clear, statistically significant activation gain.
A guided wizard with a live preview was the most impactful change. It asks short questions, such as what kind of project you are building and what you want to track, using big easy buttons. The left half of the screen takes input while the workflow assembles on the right.
Users found building basic scaffolding too much work and needed guard rails. She is not sure the tooltip is dead, and thinks the wizard fits products with high cognitive load.
Isford shipped one generic flow first, then personalized. The team judged that a single flow served over 90 percent of needs. Personalization came only after the generic version worked.
Research on real behavior showed user clusters, such as a technical user with database experience versus someone trying a colleague's tool.
She segments by learning and building style, not job role. Buckets like visual learner versus data-forward builder beat classic segments such as marketing, product or operations. A research team defined the types outside production, and sign-up questions route each person.
A teammate invited only to update a sprint needs a very different onboarding from a builder. She says there is a lot of low-hanging fruit in personalizing onboarding.
Isford keeps advanced features off day one. Someone who has never built a workflow does not need automations yet. The team split necessary education from ongoing education, and the pop-up tips called 'the mole' move users from beginner to intermediate to advanced.
She credits the lift to hours spent with customers before designing. What a user needs to be onboarded well differs from what the business wants them onboarded to, and she says to keep the two separate.
Isford prefers a hard activation metric that few users reach. Airtable used week-four multi-user: more than one person on a team active and contributing to a workflow in the fourth week. She likes metrics that 5 to 15 percent of users hit over ones that 40 percent hit.
If 40 percent are active at week four, only a fraction remain at months 12, 18 and 24. Lifting a 5 percent group to 6 or 7 percent would have large downstream effects.
She splits the metric into components before building anything. Airtable asked how many sign up as a team versus an individual, and how many reach week four. It compared people invited, ever active and active in week four, and defined what counts as active.
This work came right before the onboarding rebuild and showed where the biggest levers were.
Companion metrics stopped lopsided wins. Airtable added individual week-four retention and Build, a sophistication score, beside team activation. Some treatments made users more sophisticated without inviting teammates, and others kept people around without better building.
She says "this group of metrics actually really set us free".
Isford adds guardrail metrics next to every North Star. A North Star lets a team focus on one result, while guardrails catch wins that hurt the business. An onboarding win that causes a 10% revenue drop is her example.
When a guardrail drops, the team should dig into which part of the onboarding caused it. Analysts, PMs, engineers and designers all share that rigor.
She holds a North Star for six months, then changes it on purpose. Stability builds momentum, domain expertise and compounding impact. After that, a metric that feels like old news may mean the team has outgrown it.
She starts by drawing the funnel on a whiteboard, and says the metric should measure whether the strategy is delivering, not dictate the strategy.
Airtable moved its growth North Star from revenue to user growth. Chasing revenue led to short-term decisions. The team took a decades-long view, since users could be converted to paying customers later.
In product-led sales the goal is often a handoff to sales for an Enterprise contract, so delaying revenue can make sense. Changing a North Star is a big deal because it ripples through several teams.
She treats A/B tests as risk mitigation, not a default. Every test costs engineers, analysts and PMs time that could go to roadmapping, foundational analysis or shipping. Measuring activation at 6% versus 7% adds little beyond a line in a performance review.
Her alternative is more time with customers, a sharper problem definition and mocks shown to people, so the team ships with conviction.
Airtable shipped a form-copy feature with no A/B test. People who fill in an Airtable form had no way to keep a copy of their answers. The team added one, gated on creating an account, because customer analysis showed demand.
They accepted that signup rate or activation mix might shift, and used attribution to analyze the effect after launch. Her example is wanting a copy of the T-shirt size you emailed for a swag order.
Isford says leaders must reward impact that is not a metric lift. If engineers must point to numbers to prove their impact, the team will bias toward experimenting on everything, which she calls a very expensive cost for the business.
Qualitative feedback, deals closed and deals not lost can show a team did right by customers. It works best when the head of growth sets the tone, and it cannot excuse sloppy building or vague customer needs.
She avoids naming features in tooltips. A tooltip saying 'this is automations' announces the feature and leaves a new user unsure it fits, or even what the word means.
She says "try not to name features it can be very tempting in practice even though it sounds easy in theory". Better is a one-touch turn-on or setting up the automation to finish the user's workflow.
Isford refuses to build onboarding around the pricing scheme. Pushing a premium feature like automations early is tempting when users of it often pay. It does not help a new user get started.
She roots onboarding in the customer's need and maximum value, not the packaging or the company's interest.
She favors a reverse trial: a free plan plus a premium trial. A trial of 7, 14 or 30 days shows everything the product can do, then users fall back to free. It adds paid conversion on top of user growth and brand awareness.
The choice should follow how the company wants to monetize, and she suggests stepping back from competitors' pricing pages. A free plan for tens of millions of people values user base and brand over revenue.
She gives sales-led products a way to show value with no human present. Options include a sandbox or demo, custom landing pages, and sign-ups that lead to education before any option to pay.
When a Fortune 500 customer already has a contract, someone signing up from the same email domain can get an experience built for contracted organizations, which grows the account.
She frames PLG growth as join, evaluate, upgrade, expand. Join is signing up, evaluate is seeing the product will deliver value, upgrade is converting by card or sales, and expand is adoption spreading through the organization.
She chose 'evaluate' over 'onboard' or 'activate' because it is about what users need to see. Expansion drives net dollar retention and renewals, and feeds referrals back into join.
Isford uses the funnel as shared language, not as four KPIs. A team can explain why it invests in landing pages for join over onboarding for evaluate, and revisit the choice over time.
She says it should not map exactly to team structure or to four metrics.
Airtable's growth teams followed the funnel, with expand added later. Acquisition owned join, activation sat closest to evaluate, and monetization owned pricing and upgrade, plus churn prevention, downgrades and some billing projects.
An expand team came only once larger companies were using the product. She calls it an example of revisiting priors and staying agile in org structure.
She says B2B growth needs far more customer contact than consumer growth. With fewer customers and concentrated revenue, high-volume experiments are not available and a few customers can be a large share of revenue.
She leans on customer conversations, beta tests, live prototypes and demos. She says "face time with the customer is significantly more important than it is in b2c".
Isford hires growth people for intrinsic drive to have impact. Her interview question is to describe a time they delivered something impactful, and she listens for how the person defines impact.
She gives new reports Bob Iger's The Ride of a Lifetime.
Airtable