How Product Leaders Sell Ideas, Simplify Products, and Build Growth Loops

Casey Winters began his career as an analyst at Apartments.com on the marketing side, where he measured channels such as SEO, AdWords, affiliate marketing, and email for effectiveness. Once he got good at measurement, he started optimizing those channels directly and doing user research to understand how the product could convert leads better. The company then labeled him a marketing-and-product hybrid and did not quite know what to do with him because the two functions were separate departments.

At Grubhub, where he was the 15th employee, leadership told him they did not care whether he worked on marketing or changed the product as long as more people ordered food. He worked on growing the demand side from Series A to IPO, and his team eventually created a product management function, though for the first four years they did not use product titles. At Pinterest he was formally labeled a product person and led the growth product team, rebuilding the growth model as the company went from 40 million to 150 million monthly active users. He later advised Airbnb on the demand side and worked with Pocket, Greylock Partners, Eventbrite, Tinder, Thumbtack, and Canva before becoming Eventbrite’s chief product officer.

Casey observed during the pandemic at Eventbrite that many managers and leaders tried to deal with issues on their own rather than escalate them. When goals were missed, he would hear that the situation was impossible and that many things had gone wrong. His response was that he could not understand the situation if nobody told him about it, and that the right move is often to escalate so a leader can either change the circumstances or at least understand the explicit trade-off.

He believes people generally undercommunicate upward and then complain that executives are out of touch. When people do communicate upward, they often start too deep in the weeds, so executive questions feel like a different language. He coaches his team to start with “chapter one”: the part of company strategy they are working on, the metrics they are trying to improve, and the assumptions guiding what they are building. Many presenters instead start at “chapter six,” skipping the context that would earn them the right to tell that part of the story.

The opposite failure is spending the first 20 minutes re-explaining company strategy or who the customer is to people who already know it. Casey advises finding the last point in the story that is completely obvious to the audience and moving from there into less obvious material they can follow. He coaches before the meeting rather than after, because big reveals create success-or-fail moments. He role-plays the audience—what the CFO will ask, why the CEO will ask it—and pushes pre-meetings so major concerns surface before the high-stakes review.

Casey cites Scott Belsky’s product life cycle: users flock to a simple product, the product takes users for granted and adds features for power users, and users flock to the next simple product. He has studied design hacks companies use to avoid that cycle, including unbundling complex functionality as Facebook Messenger and Uber Eats did, progressive disclosure at Pinterest, proactive training, and segmenting experiences by user type. None of those worked cleanly for Eventbrite.

Eventbrite serves creators putting on their first event with five expected attendees as well as creators running 100 events a year, and users can move between those categories as their businesses grow. Segmentation and progressive disclosure therefore do not fit well, because the company never wants some users to find advanced functionality that would confuse them. The aspiration is “perceived simplicity”: advanced features are easily discoverable when someone looks for them but effectively hidden when they are not. WhatsApp is his model—a chat app at its core where voice messages, video calls, and phone calls are easy to learn when needed but not in the way.

On Eventbrite’s marketing side, the company built automation for creators’ Facebook advertising, supercharged by Eventbrite’s data. Some creators want to geek out on targeting and creative, while many want the work done for them. The product now defaults to a simple experience where Eventbrite handles targeting and creative, with an on-ramp for creators who want more control. Casey calls this an area where the team has not perfected the model but now understands the different user types and gives both a path to success.

Casey argues that at scale, some of the most impactful work is the hardest to measure—user experience, performance, developer velocity, or product areas deemed unsexy—so it gets chronically underfunded. The old adage applies: what gets measured gets managed. Tactics that help include building custom metrics, running small tests that prove the investment’s worth, creating team principles so important elements are not forgotten, and using experiments to build broader buy-in. It also requires a coalition: the product manager, engineering manager, and design leader need to agree that performance or user experience needs work.

Once two or three people are aligned on an unsexy problem, it becomes easier to build a game plan around metrics, small tests, or OKRs that show massive impact. That evidence can then get the rest of the company excited to invest. Casey also pushes teams to recognize that a scaled business can lose what it has already built. At Pinterest, growth stopped after changes in the Facebook market, and later an SEO algorithm change severely affected growth once Pinterest relied primarily on SEO. Those experiences built intuition that past gains are not guaranteed and that protecting what exists becomes more important at scale.

He points to a chart of product-market fit over time to make the same point: user expectations keep rising and competitors keep improving. If a company does not continually improve its product, user experience, and latency, it may fall out of product-market fit—not necessarily tomorrow, but in a year or five years. Recovering from that position takes time and often requires cleaning up technical debt to catch up to market expectations. Doing work to avoid that situation is extremely valuable.

Casey’s post on operations roles began with an essay on martech and a realization that a conference for the growth of the marketing operations professional represented something he did not want for the industry. He says “having marketing ops means you suck at marketing” is hyperbole, and he is not against marketing ops or product ops as roles—Eventbrite has a product ops team. But he ran a double-digit-million-dollar marketing budget at Grubhub without marketing ops because the team invested in automation and process. He worries when the first tactic for scaling is adding people.

The problem is normalizing ops as a distinct, stable function where the job is to perform a manual process long term. At Eventbrite, he says the ops team’s explicit job is to find inefficiencies and build process or software to root them out, then move on to other valuable work. He cites an Intercom blog post that says the goal of business operations did not exist. Functional ops roles can be a hack for a functional issue, but building larger and larger operations teams can exacerbate the efficiency problem rather than fix it.

He calls that pattern a form of empire building, which he has little tolerance for. The goal should be to make the function operate with fewer people and more value, even if that means a product operations job is no longer needed in a year. If someone has done a great job rooting out inefficiencies, other parts of the company should want them for new work. He notes that at Airbnb many strong ops people moved into other roles once their original role was no longer necessary, and teams wanted them because they had been effective.

Casey defines the CPO job as leading and facilitating the development of products and features that deliver value for Eventbrite’s customers and translate into value for the business. The function can include product management, product design, research, and growth marketing, depending on the company and the leader’s skill set. He says his job is to make sure Eventbrite chooses the best product strategy it can from the information available, adjusts as the team learns, and builds a feedback loop. He also owns defining and improving the process for setting strategy, prioritizing projects, executing, communicating with the rest of the company, removing bottlenecks, training the team, and hiring.

He is accountable for what the team builds and for improving the conversion rate and magnitude of impact over time. Not everything will drive value, but he wants most of it to, and he wants the impact to get larger. On the path to CPO, he calls his journey irregular: he focused on where he thought there was leverage, learned as much as he could about the entire business, and worked on high-impact problems regardless of org structure or career path. The CPO role is more company leadership than functional leadership, so he had to learn to optimize for the whole company even at the expense of his team.

Working with executives since his first job helped him learn their language and what they cared about. He advises assuming that executive questions are attempts to learn rather than tests, which changes the interaction. He also refused to specialize, believing that combining skills would let him work on the most important problems rather than only what he already knew. That led to slower visible progress in titles, but a faster path to a true executive role because he could speak with CEOs about more topics than most peers.

Casey describes a spectrum of product people inspired by a conversation with Omar, who runs product at Cambly and formerly ran core product at Pinterest. On one side are “crazy innovators” with many ideas, attention to every industry change, and knowledge of the latest APIs and features; most ideas are bad, but one in ten can be a game changer, and they are generally not great at turning ideas into action. On the other side are execution-focused product managers who can take a strong strategy and turn it into customer value but may not know what is happening in the industry or generate a new product idea without direction. Companies want people in the middle: strategic enough to generate good ideas and executional enough to deliver them, but those people are rare.

As a CPO, Casey biases toward execution over idea generation because companies have too many ideas and need to focus and execute on the best ones. A venture capitalist would bias the other way, since one huge winner among ten crazy ideas can make the fund. The practical challenge is that product leaders recruit and grow many executional people, but moving them to director or CPO level requires more strategic ability. He is trying Reforge programs, mentorship, outside speakers, and other tactics to move more of the team toward the middle, though he calls it a work in progress.

Early in a product career, the most valuable thing is showing that you can ship real things customers like. To manage groups of product managers or run a business unit, however, a CPO will expect someone to write the strategy document without help. Casey has seen many people unable to make that step, which caps them at senior product manager or group product manager because they cannot show they can drive decision-making and push new ideas forward. He calls strategy ownership the great filter for reaching top product leadership.

Casey does not see many genuinely new growth channels, unless one counts web3 tokens, which he does not. Instead, he sees companies getting more leverage from existing channels through better flows and lifetime value. At Eventbrite, the team unified separate direct-response and lead-generation flows in performance marketing to acquire creators, which reduced effort, improved CPAs, and let sales pick up product-qualified leads from direct-response customers who needed more help. He calls this product-led: unifying self-service loops and sales loops in a B2B business into one larger loop that breaks down silos and operates more efficiently.

He is excited about founders building growth loops into the product before product-market fit—not to scale prematurely, but so that when they find product-market fit they have a built-in distribution advantage. He argues that scalable acquisition, or an acquisition loop, is a requirement for product-market fit; a product that retains well but cannot find more users is not, in his view, product-market fit. On timing, he says growth should not be the focus before the product works, but founders should think early about how the product can grow scalably. Early growth should be done by founders through “kindle” strategies: non-scalable hacks that get early users and exist to unlock “fire” strategies such as content loops, sales loops, viral loops, and paid acquisition. Once a fire strategy is unlocked, that is when to hire a full-time growth person—a salesperson, growth PM, or performance marketer—to make it 10x better.

Casey still thinks data network effects are underrated, and he distinguishes them from selling data as a product. Data network effects mean leveraging product usage data to make the product’s value stronger over time, such as personalized results at Pinterest or better targeting data for advertising at Eventbrite. With changes from Facebook and Apple, a product that can generate its own data rather than relying on big platforms has a real edge. He says this has worked well for him at Pinterest and now at Eventbrite.