When I think about building enduring startups, one principle guides my approach: treat the company itself as the product. That mindset came into sharp focus as I studied the operating systems behind Kevin Fishner, Chief of Staff at HashiCorp. The rigor and clarity of his approach offer a blueprint any product management leader can adapt to scale with speed and integrity.
As the first business hire at the cloud infrastructure automation company, he previously built out the sales, marketing and product management teams. That trajectory matters: it’s rare to see one leader connect go-to-market, product management, and operational cadence so cohesively. The result is a system that aligns strategy, execution, and learning loops without creating organizational drag.
Now as chief of staff, he’s focused on building a strong foundation of company-wide systems, now that the team has grown to over 1000 people. This is where great product management leadership shines—codifying how decisions are made, how work moves, and how teams align around outcomes as headcount and complexity expand.
In today’s conversation, Kevin shares a detailed look at how they run meetings, set and track progress toward goals, and make decisions through writing at HashiCorp. I’m a strong proponent of a writing-first culture as the backbone of a scalable operating cadence: crisp memos reduce meetings, strengthen decision quality, and preserve context. Combined with clear meeting charters, owner-defined agendas, and time-boxed decision-making, this turns process into a lever for speed—without sacrificing rigor.
He also shares incredibly tactical advice for making annual planning more effective, including the unique business simulation they run, their scorecard system, and the weekly and quarterly meetings that help them stay focused on important KPIs. My lens: anchor annual planning in outcomes vs output OKRs, then connect those outcomes directly to product roadmapping and sprint planning. Use QBRs vs OKRs thoughtfully—QBRs to pressure-test business performance and assumptions, OKRs to lock in the next set of measurable bets. The scorecard becomes the single source of truth for progress and trade-offs, while the business simulation stress-tests priorities before they hit roadmaps.
Whether you’re a chief of staff, a founder spinning up a company from scratch, or a manager scaling a team, you’ll find practical takeaways here to make your organization more effective. I’ve distilled templates, prompts, and visuals to help you adopt a writing-first decision model, stand up a repeatable meeting rhythm, and operationalize goal tracking so KPIs stay front and center—not buried in dashboards.
If you’re serious about building startup systems that scale, adapt these practices: align on a few critical outcomes, document decisions in writing, instrument scorecards that ladder to KPIs, and commit to weekly and quarterly cadences that turn strategy into execution. That’s how you build an organization that learns faster than it grows.
Inspired by this post on First Round.
Leave a Reply