I’ve spent enough cycles scaling product organizations to know that leaders grow—or their companies stall. In this reflection, I distill the practices I rely on to scale an org, develop myself, and raise the performance ceiling across teams, especially when the economic environment demands sharper focus and better decisions.
To ground this discussion, I often point leaders to exemplary people-first operators. Jack Altman is the co-founder and CEO of Lattice, a people success platform for building engaged, high-performing teams. Lattice has raised over $330M, and was last valued at $3B. His work on culture and performance—captured in “People Strategy”—reinforces many of the principles I use daily.
I start with self-awareness because it’s the keystone. If I can’t see my own patterns—when I’m avoiding conflict, over-controlling, or confusing activity with outcomes—everything else degrades. I cultivate self-awareness by writing brutally honest weekly retros, asking my staff for one piece of constructive feedback every month, and running periodic 360s to reveal blind spots. The goal isn’t comfort; it’s truth. When I improve my signal on reality, my decisions get faster and my team gains confidence.
Difficult conversations are a gift to performance. I’ve learned to tackle them quickly, with empathy and specificity. I name the gap between expectation and outcome, share observable examples, state the impact on the team, and propose a clear path forward with timelines. If emotions run hot, I slow down, seek to understand, and stay on the behavior and results—not the person. Avoidance compounds culture debt; candor repays it with interest.
Scaling a company introduces predictable failure modes. I’ve seen leaders confuse hiring errors with management errors; it matters which you’re facing. A hiring error shows up as persistent gaps in role fundamentals even after clear expectations, coaching, and time-bound support. A management error usually stems from ambiguous goals, poor context, or inadequate resources. I assume management error first and fix the environment. If results still lag, I revisit the hire.
Delegation versus control is a healthy tension. Early, I’ll “micro-mentor” on critical work to teach quality, taste, and judgment—then expand autonomy as pattern recognition develops. My rule: delegate outcomes, keep ownership of standards and context. I never give up the responsibility to set the bar for the team and to protect the product vision; those are one-way doors that define the company’s trajectory.
Building a product organization that compounds requires clarity and context. I ensure every product trio understands the strategy, customer segments, and constraints. We anchor on outcomes vs output OKRs, maintain a living strategy doc, and write decision memos that document trade-offs. When context flows, people need fewer approvals and produce better work, faster.
On so-called micro-management, here’s my take: it’s a tool, not an identity. Early in a function or with a new leader, I may be intentionally hands-on to transfer judgment. The moment competence and trust are proven, I deliberately pull back. The mistake isn’t micro-managing; it’s forgetting to stop.
CEO-level context setting is non-negotiable. I articulate the narrative behind the plan—the why, the constraints, the risks, and what we’re not doing. Transparency isn’t oversharing; it’s sharing the right information at the right fidelity so people can make aligned decisions. I model this with written updates, open Q&A, and by explaining how major calls were made.
Some of the most valuable leadership work happens in uncomfortable conversations. I prepare by drafting the core message, testing it for clarity and fairness, and deciding what success looks like for the person and for the business. I also own the decision. When the stakes are high, I don’t outsource the final call or feedback to a proxy; accountability builds trust.
Speed versus accuracy in decision-making is situational. For reversible bets, I bias to speed, time-box the experiment, and set clear kill criteria. For one-way doors, I slow down, increase the sample of perspectives, and pressure-test assumptions. I counter hidden biases in group discussions by starting with silent written proposals and independent scoring before we debate out loud.
I’ve even experimented with removing myself from recurring meetings for a cycle. The outcome: decisions kept moving, and I learned where my presence added value versus created drag. Now I show up intentionally—for feedback on taste, to unblock cross-functional issues, or to deliver context—then get out of the way.
Here are four practices that consistently pay off for me: protect deep work blocks for strategic writing, conduct weekly customer calls, review hiring quality monthly, and keep a running list of hard problems only I can solve. This keeps me oriented toward leverage, not busyness.
Talking to customers is an art. I avoid solution-leading questions and ask about current workflows, pains, and the last time the problem showed up. I go five whys deep, quantify the value of a better outcome, and listen for language customers use to describe success. The best product discovery lives in those unpolished details.
Great leaders are constant learners. I rotate through books, operator peer groups, product management leadership communities, and curated newsletters. I also treat my own organization as a learning system—post-mortems, pre-mortems, and lightweight experiments build institutional knowledge faster than any single playbook.
To maximize employee performance, I use a simple model: Clarity x Capability x Motivation x Environment. Clarity means crisp expectations and definitions of done. Capability is skills and experience, which I grow via coaching and targeted practice. Motivation blends purpose, recognition, and meaningful goals. Environment covers tools, psychological safety, and focus time. If any factor is near zero, performance collapses; my job is to diagnose and raise the lowest one.
When long-time employees stop scaling with the company, I address it early. Sometimes a role redesign or releveling unlocks success. Other times, a dignified, well-supported transition is the right call for everyone. Avoiding the issue erodes trust; handling it with clarity and care strengthens culture.
Low-performing but well-liked employees create a leadership test. I separate likability from impact. If values are strong but performance lags, I set a time-bound plan with clear checkpoints. If progress doesn’t materialize, I act. Keeping someone in a role they’re not meeting hurts the team and the individual by delaying a better fit.
When someone is let go, I’m thoughtful about what to share. I communicate the change promptly, state the role-level rationale without gossip, thank the person for their contributions, and reinforce the plan going forward. The aim is to honor privacy while maintaining clarity about standards.
In today’s tougher macro environment, I refocus on capital efficiency, ROI-driven roadmaps, and slower, more deliberate hiring. I raise the bar for product bets, validate earlier with customers, and price for value. Constraints, when embraced, sharpen strategy and execution.
Aligning career goals with company goals is ongoing work. I use growth frameworks, individual development plans, and quarterly conversations that link business outcomes to skill-building. When people see a path to mastery and impact, performance accelerates.
Most leaders underestimate their team’s potential. I raise expectations with ambitious, outcome-based goals, ensure people have the context to operate like owners, and celebrate learning velocity as much as wins. When standards, support, and trust rise together, teams routinely outperform even optimistic forecasts.
Resources I recommend: Jack’s book: https://www.amazon.com/People-Strategy-Culture-Competitive-Advantage/dp/1119717043. Jack’s company, Lattice: https://lattice.com/. First Round Capital’s Newsletter: https://review.firstround.com/newsletter.
