Author: Shivam Tiwari

  • Startup Acquisition Process: A Founder’s Operating Playbook

    Startup Acquisition Process: A Founder’s Operating Playbook

    An acquisition inquiry creates two jobs at once. You must determine whether the buyer is serious, and you must keep building the company in case the deal disappears. Confusing interest with commitment can cost you customers, product momentum, and negotiating leverage.

    The right operating model protects both paths. You qualify the buyer before expanding access, define what a good outcome means before negotiating it, and prepare integration while you still have the leverage to shape it. The goal is not simply to get a transaction signed. It is to preserve your options and make sure the company can succeed whether the deal closes or not.

    Start by writing the acquisition thesis and walk-away conditions

    A founder can enter an acquisition process with a precise view of the company’s value and still be unprepared for the decision. Valuation is only one variable. You also need to decide what should happen to the product, customers, team, and mission after control changes hands.

    Treat M&A as an extension of product strategy. The buyer should be able to create a credible future for what you have built, not merely provide an acceptable exit. If you cannot explain why this company is a better owner, the process is running ahead of the strategy.

    Write a short acquisition brief before substantive negotiations begin. It should answer:

    • Why consider a sale now? State the constraint or opportunity the transaction could address. That might be distribution, product adjacency, operating scale, or a path to greater customer impact. Do not substitute general fatigue or flattering buyer attention for a strategic reason.
    • Why could this buyer be the right owner? Name the assets the buyer would contribute and the part of the business those assets could strengthen.
    • What must remain true after closing? Define the outcomes that matter for customers, the product, key builders, and your own role.
    • What would make you stop? Record the conditions that would invalidate the deal, such as the absence of an accountable operating owner, an incoherent integration plan, or terms that put unacceptable obligations on founders and employees.
    • What evidence would change your position? Decide what the buyer must demonstrate before you increase access, incur more diligence cost, or make a binding commitment.

    This brief prevents each new conversation from redefining success. It also gives you a concrete basis for aligning investors. Agree on valuation guardrails, who can negotiate which issues, and what information will be shared with whom. Investor disagreement is much harder to resolve after a buyer has created urgency around a particular outcome.

    Do not treat the brief as legal or financial analysis. An acquisition can create material tax, contractual, employment, and fiduciary consequences. Qualified M&A counsel and financial or tax advisers should evaluate your specific situation before you sign anything that commits the company or limits its alternatives.

    Qualify the buyer before you expose the company

    An interested company is not yet a qualified buyer. Approach it with the discipline you would apply to a large enterprise prospect: identify the economic owner, understand the use case, map the decision process, and look for evidence that the organization can implement what it says it wants.

    Corporate development may coordinate the transaction, but it usually cannot answer every operating question. You need access to the executives who would sponsor, fund, sell, integrate, and run the acquired business. A productive buyer map includes the executive sponsor, the general manager or P&L owner, product and engineering leaders, the sales leader responsible for the customer story, and the finance leader modeling the expected value.

    Qualification areaQuestion to askEvidence to look for
    Executive sponsorshipWho has the authority and incentive to get this transaction completed?Direct access to a named senior sponsor who can explain the strategic objective.
    Product adjacencyWhich existing product, customer need, or strategic priority does the acquisition advance?A concrete use case that connects your product to the buyer’s roadmap.
    Operating homeWhich leader and P&L will own the business after closing?A clear organizational destination, decision owner, and resourcing discussion.
    Integration pathHow would the organizations and technologies fit together?Participation from the product, engineering, security, and operating leaders who would do the work.
    Customer valueWhy will customers be better served after the transaction?A joint customer narrative that survives detailed questions from sales and customer-facing teams.
    Builder continuityWhich people are essential to the product’s future?Early, specific discussion of roles, reporting relationships, and retention.

    Separate buying signals from meeting activity

    The strongest buying signals require the buyer to spend political or operational capital. These include fast access to senior decision-makers, serious technical and security diligence, direct discussion of deal structure, work on an integration plan, and effort to develop a customer narrative. Those actions indicate that people beyond the deal team are preparing to own an outcome.

    Weak signals are easier to generate. Vague strategic interest, meetings without a decision owner, reluctance to explain organizational ownership, and a continuing sequence of introductory conversations can consume your attention without moving the buyer toward a commitment. Rapid senior access and substantive integration work are more meaningful than the number of meetings on the calendar.

    When the signal weakens, ask for the next decision rather than the next conversation:

    • What decision is the buyer trying to make now?
    • Who owns that decision?
    • What information is actually needed to make it?
    • What will happen if the answer is positive?
    • Which operating executive will participate in that next step?

    If the buyer cannot answer, narrow access or pause the process. That is not a negotiating stunt. It is focus management. Your company should not perform open-ended diligence for an organization that has not defined its own intent.

    Run diligence without starving the operating business

    Acquisition work expands quietly. A founder answers a request, invites a functional leader, and soon half the leadership team is preparing custom material for a deal that remains uncertain. The damage usually appears later: delayed product decisions, slower customer follow-up, employee speculation, and a weaker standalone plan.

    Set up a separate operating system for the transaction. Keep the early circle small, designate one deal lead, use a controlled data room as the single source of truth, and send a weekly update to the people who are authorized to know. The update should cover decisions made, open requests, major risks, next gates, and any work that could disrupt the core business.

    Make every diligence request earn its cost

    A data room is not an invitation to upload everything. Organize approved material by the questions a credible buyer must answer: the product and technology, security posture, commercial performance, customers, people, corporate records, and financial or contractual obligations. Have counsel control sensitive disclosure and any information affected by confidentiality, privacy, employment, or regulatory duties.

    Route new requests through the deal lead. For each request, record:

    • The buyer’s decision that the information supports.
    • The person on the buyer’s side responsible for reviewing it.
    • The least disruptive way to provide a reliable answer.
    • Whether the material is already available in the data room.
    • Any confidentiality, customer, employee, security, or legal constraint.

    This exposes duplicate and exploratory requests before they reach the team. It also prevents inconsistent answers from being created in separate email threads.

    Protect the company on three parallel tracks

    The work should remain visibly separated:

    • Standalone execution: Keep shipping, serving customers, managing cash, and pursuing the plan that makes the company viable without the transaction.
    • Transaction execution: Coordinate buyer communication, diligence, investor alignment, advisers, document control, and negotiation.
    • Post-close readiness: Develop the retention, customer communication, ownership, and integration plan needed if the transaction becomes likely.

    The first track is your source of optionality. If it degrades, your leverage becomes dependent on the buyer’s continued interest. Review transaction demands against operating commitments and move work away from product or customer owners when it can be handled by the deal lead or an adviser.

    Prepare for employee questions before rumors appear

    Broad disclosure too early can create anxiety and unnecessary distraction. Secrecy without a communication plan creates a different risk: managers improvise when employees notice unusual meetings, adviser activity, or information requests.

    Limit knowledge while uncertainty is high, but prepare an approved response for managers if questions surface. It should avoid confirming confidential negotiations, avoid making promises about jobs or roles, and tell employees how material information will be communicated. Have counsel review the wording when contractual or disclosure obligations could apply.

    Once a transaction becomes likely, expand the communication plan deliberately. Identify who needs to hear what, in what order, and from whom. Employees, customers, partners, and investors have different concerns; sending all of them the same generic announcement leaves the most important questions unanswered.

    Negotiate the operating future, not only the transaction

    A high headline value can conceal an unclear operating future. Deal structure, individual obligations, retention arrangements, decision rights, resourcing, and the buyer’s integration choices can materially change what the outcome means. Do not compare offers or commitments by headline value alone. Your legal, tax, and financial advisers need to assess the complete terms and the risks attached to them.

    At the same time, advisers cannot decide whether the strategic operating model makes sense. You need direct answers from the executives who will own the business:

    • Who is accountable for the acquired product after closing?
    • Where will the product and team sit in the organization?
    • Which decisions will remain with the current leaders, and which will move to the buyer?
    • How will success be measured?
    • What people, budget, distribution, and technical support will be committed?
    • Which builders are considered essential, and what roles will they have?
    • How will existing customers be supported through product and commercial changes?
    • What integration milestones must be completed before the strategic thesis can be tested?

    Push for names and commitments. Phrases such as “access to scale” or “strategic alignment” are aspirations, not an operating plan. A credible plan identifies an owner, a destination in the organization, a success measure, and resources. If no P&L will house the asset and no executive owns the outcome, assume the acquisition will compete with the buyer’s existing priorities after the negotiating attention disappears.

    Use diligence as joint problem-solving. Share relevant roadmap choices, customer wins, and integration hypotheses, then ask the buyer’s product, engineering, sales, finance, and operating leaders to challenge them. This does more than test strategic fit. It reveals how those leaders make trade-offs and whether the working relationship can survive post-close pressure.

    Plan day one while you still have negotiating leverage

    Do not wait for the signature to begin thinking about implementation. Retention, customer communication, and integration milestones should be developed as the deal becomes likely. Waiting until after closing turns unresolved assumptions into operating facts.

    Your readiness plan should specify:

    • The leader who will own the acquired product and the cadence for resolving integration decisions.
    • The success metrics that connect the transaction thesis to customer and business outcomes.
    • The first communication for employees, customers, and partners, including who will deliver each message.
    • The roles and reporting relationships of key builders.
    • The product, technical, security, and commercial integration milestones that require named owners.
    • The customer commitments that must remain visible during the transition.

    Where the buyer will not define these points before closing, record the uncertainty explicitly. An unresolved question is a risk to evaluate, not an empty box that optimism should fill.

    Key takeaways for your next buyer conversation

    • An acquisition inquiry is not an offer. Qualify intent before allowing the process to consume the company.
    • Define a successful outcome and your walk-away conditions before the buyer creates momentum around its preferred terms.
    • Look for an executive sponsor, product adjacency, an operating home, committed resources, and a credible integration path.
    • Treat senior access, technical and security depth, structural discussions, and joint customer planning as stronger signals than meeting volume.
    • Keep the early circle small, centralize approved information, and use a weekly update to control decisions and workload.
    • Maintain a standalone operating track. Product and customer execution are both business necessities and sources of negotiating leverage.
    • Evaluate the complete legal and financial structure with qualified advisers; headline valuation does not describe the full outcome.
    • Negotiate ownership, decision rights, success metrics, retention, customer communication, and integration before those assumptions become post-close problems.

    Before your next acquisition meeting, create an acquisition brief and a buyer qualification scorecard. Then ask the buyer to identify its next decision, the executive who owns it, and the operating leader who would own your product after closing. Those answers will tell you whether to invest further in the process or return your attention to building the company.

    References

  • How to Turn Product Adoption Into a Product-Led GTM System

    How to Turn Product Adoption Into a Product-Led GTM System

    Your signup chart is moving, but too few customers are changing how they work. Marketing wants more traffic, sales questions lead quality, and product points to a healthy activation rate. Each function may be reading its own dashboard correctly while the business still has an adoption problem.

    The way out is to make adoption the shared operating unit for product-led go-to-market. Define the behavior that proves durable value, identify what prevents customers from reaching it, route each account according to evidence, and measure the transitions between those states. That turns product-led growth from a collection of tactics into a system you can manage.

    Define adoption as a customer behavior, not a company milestone

    A signup is an acquisition event. A payment is a commercial event. Neither proves that the product has become part of the customer’s operating rhythm.

    Adoption occurs when the right customer repeatedly uses the product to complete a meaningful job. That definition needs to be observable in product data, specific to an ideal customer profile, and tied to the natural cadence of the work. A payroll workflow, a daily support queue, and a quarterly planning product should not share the same return window.

    Write an adoption contract before debating channels, onboarding screens, or product-qualified lead scores. It should answer five questions:

    1. Who must adopt? Name the account segment, role, use case, and relevant starting condition. New teams migrating from another system may face a different path from first-time users.
    2. What job must be completed? Describe the customer outcome rather than a feature interaction. Creating a project is weaker evidence than using that project to complete a real handoff.
    3. Which event proves first value? Select the smallest observable action that demonstrates the promised outcome. Avoid events chosen merely because they are easy to instrument.
    4. What repetition proves adoption? Require a return to the workflow within its normal operating cycle. Do not choose an arbitrary number of sessions because it produces a tidy chart.
    5. What scope makes the behavior durable? Depending on the product, that may involve live data, a teammate, a critical integration, a second workflow, or another signal that switching back would sacrifice real value.

    For a collaborative workspace, for example, account creation may be activation. Adoption may require an operations lead to import a live process, a teammate to complete a handoff inside it, and the account to repeat that workflow in the next normal cycle. The exact event is product-specific; the discipline of connecting it to a completed job is not.

    Keep the funnel states separate:

    • Acquisition: A relevant user or account arrives.
    • Activation: The customer experiences initial value.
    • Adoption: The customer incorporates the workflow into real work.
    • Retention: The behavior persists across later cycles.
    • Expansion: More people, workflows, usage, or spend accumulate around that value.

    This separation prevents two common misreads. A customer can pay before adopting because procurement moved faster than implementation. A user can also be highly engaged while the wider account remains untouched. For a B2B product, track both user-level behavior and account-level penetration so one enthusiastic champion does not conceal a stalled rollout.

    Diagnose the barrier before choosing the growth tactic

    When adoption stalls, teams often add another tooltip, email sequence, demo, or discount. Those tactics address different problems. Applying all of them at once increases noise and makes the result harder to interpret.

    A more precise diagnosis starts with five barriers: reactance, endowment, distance, uncertainty, and corroborating evidence. The practical question is not how to push the customer harder. It is which barrier makes the next behavior feel unattractive, unsafe, or unnecessarily difficult.

    BarrierWhat you may observeProduct responseGTM response
    ReactanceUsers resist a mandatory rollout, aggressive prompt, or seller-controlled process.Restore choice with opt-in paths, reversible actions, and control over timing.Offer a bounded pilot and a clear decision process. Use real trigger events instead of manufactured pressure.
    EndowmentThe current tool or manual workflow is familiar, connected, and politically safe.Support imports, integrations, saved state, and temporary coexistence with the incumbent workflow.Provide a migration plan and compare the cost of staying put with the cost of switching.
    DistanceThe target behavior asks for too much change before any value appears.Break setup into progressive steps, preconfigure sensible paths, and reveal advanced work later.Start with one use case, team, or milestone rather than asking for an organization-wide commitment.
    UncertaintyThe buyer cannot predict the result, effort, security implications, or reversibility.Use previews, sample states, validation, undo paths, and visible progress.Define pilot scope, success criteria, responsibilities, and the decision that follows the pilot.
    Corroborating evidenceA champion sees the value but cannot persuade peers, executives, security, or procurement.Surface relevant examples, completed outcomes, and artifacts the champion can share.Equip the account with credible customer evidence, an ROI model, references, and proof from comparable situations.

    The same funnel symptom can come from different barriers. A customer who abandons an integration may fear data risk, lack technical help, or see too little value to justify the effort. A customer who completes a pilot but does not expand may need peer evidence, procurement support, or a smaller second step. Conversion data tells you where the journey broke; interviews, support conversations, session evidence, and sales objections help explain why.

    Use a one-barrier test for each intervention:

    1. Name the blocked segment and the next behavior you expected.
    2. Write the barrier hypothesis in plain language.
    3. Change one part of the experience that directly lowers that barrier.
    4. Measure movement into the next funnel state, not clicks on the intervention itself.
    5. Check a guardrail such as errors, support demand, low-quality activation, or later retention.

    This also changes how you create urgency. If a seasonal event, contract renewal, operating milestone, or compounding benefit creates a real window, make it concrete. A false deadline may produce a response while increasing reactance. The goal is an informed next step the customer still experiences as their decision.

    Connect onboarding, intent signals, and human help

    Product-led GTM does not mean leaving the product to do every job. It means using product behavior to deliver value and decide what kind of assistance the customer needs next.

    Make onboarding complete the promised job

    The first product session should continue the promise that brought the customer in. If an acquisition page promises a faster client handoff, onboarding should help the user complete that handoff. A generic tour of navigation, settings, and unrelated features breaks the connection between intent and value.

    1. Preserve acquisition context. Pass the use case, role, template, or integration named before signup into the first-run path.
    2. Start with the smallest real input. Import live work, connect a relevant system, or create a realistic first object. Sample data can teach mechanics, but it should lead clearly to the customer’s own data.
    3. Delay nonessential requests. Ask for permissions, profile fields, configuration, and invitations when they become necessary for the next unit of value.
    4. Guide the next action in context. A prompt should help complete the workflow now, not advertise a feature that might matter later.
    5. Make value visible. Show the completed outcome, saved effort, collaborator response, or operational change the customer came to achieve.
    6. Provide a recovery path. Preserve progress, explain errors, expose remaining steps, and offer human help when the blocker cannot be solved safely in the interface.

    Migration deserves product ownership because it is often the adoption experience, not an implementation detail. Imports, mappings, validation, rollback, and phased rollout reduce both switching effort and the perceived loss of the old workflow. If the customer must reconstruct years of context before seeing value, a polished welcome screen will not rescue activation.

    Route accounts by fit, value, and complexity

    Intent models become useful when they combine customer fit with behavioral evidence. Useful inputs include acquisition-source quality, setup depth, completion of the first-value milestone, collaboration signals, and connection to a critical integration. A page view may show curiosity. Repeated use of a live workflow with teammates is stronger evidence that the account has something worth expanding.

    Do not assign permanent weights based on intuition. Start with an explicit model, then compare each signal with later adoption, conversion, and retention. Remove signals that create activity without predicting value.

    • Good fit, no first value: Route to use-case education, concierge onboarding, migration help, or a simpler setup path. A sales pitch is unlikely to solve an unfinished product experience.
    • Activated, low complexity: Keep the path self-serve. Use contextual guidance, transparent packaging, and a clear upgrade moment tied to value.
    • Activated, high complexity: Add sales assistance when security, procurement, integration design, rollout coordination, or a multi-stakeholder decision requires a person.
    • Adopted, limited breadth: Use customer education or customer success to introduce the next relevant team or workflow. Do not push an unrelated feature merely because it is available.
    • Strong usage, weak fit: Preserve an efficient self-serve experience and examine whether the segment belongs in the ideal customer profile before committing expensive assistance.

    A product-qualified lead should therefore mean more than an active user. It should combine account fit, evidence of realized value, and a buying or expansion condition that human involvement can improve. This definition gives sales a reason to trust the signal and gives product a standard beyond raw engagement.

    Marketing, product, sales, customer success, community, and communications each have a distinct role. Marketing attracts the right customer with the right problem and prepares that customer to succeed. Product owns the path to initial and repeated value. Sales resolves complexity and coordinates a consequential purchase. Customer success helps an adopted workflow spread and persist.

    Community and creator programs can extend education when customers benefit from templates, integrations, examples, and shared workflows. Start with tighter curation when quality or compliance matters; decentralize more as the operating rules become clear and capable users emerge. Executive communications can reinforce category clarity and trust, but it should support the product-led motion rather than be treated as predictable customer acquisition.

    Run adoption as a measurable operating loop

    A single top-line dashboard cannot tell you whether the company has an acquisition, activation, adoption, monetization, or retention problem. Build a scorecard around transitions between those states and keep each denominator stable.

    Measure the path to durable value

    • Qualified acquisition: The number of new users or accounts that match the segment and use case in the adoption contract.
    • Activation rate: Qualified new accounts that reach first value divided by qualified new accounts entering the path.
    • Time to first value: The elapsed time from the meaningful starting event to activation. Report the median and inspect the distribution so a small set of long implementations is not hidden.
    • Adoption conversion: Activated accounts that meet the repeated-behavior definition divided by activated accounts eligible to do so.
    • Depth: How much of the core workflow is completed inside the product, using live work rather than incidental activity.
    • Breadth: How far the adopted behavior has spread across the relevant users, roles, teams, or workflows in the account.
    • Behavioral retention: The share of adopted accounts still completing the core job in later natural usage cycles.
    • Monetization and expansion: Paid conversion, usage growth, additional seats, or wider workflow coverage that follows realized value.

    Segment every transition by ideal customer profile, use case, acquisition source, onboarding path, and assistance type. Aggregate numbers can improve simply because the mix changed. Cohorts show whether a product or GTM change helped comparable customers move further through the journey.

    The shape of the funnel gives you a practical diagnostic:

    • If qualified acquisition rises while activation stays flat, inspect message-to-product continuity, setup friction, and channel quality.
    • If activation improves while adoption does not, the first-value event may be too shallow or the second-use path may contain the real friction.
    • If adoption is strong while paid conversion is weak, inspect packaging, entitlement boundaries, pricing logic, and whether the buyer is distinct from the user.
    • If paid conversion is strong while behavioral retention is weak, commitment may be arriving before durable value. Inspect implementation and post-purchase cohorts.
    • If sales assistance increases without improving adoption or conversion, the handoff may be too early, the segment may be wrong, or the human motion may be repeating work the product should complete.

    Do not scale acquisition merely because one early-stage rate moved. More traffic magnifies whatever happens after signup. Scale a channel when the relevant cohort can activate, adopt, and retain at a level that supports the commercial model.

    Give every experiment a decision rule

    Use a one-page experiment brief with seven fields: target segment, blocked behavior, barrier hypothesis, proposed change, primary transition metric, guardrail, and decision date. Set the observation window from the natural usage cycle rather than the team’s meeting calendar.

    A practical cadence keeps learning fast without rewarding noise:

    • Daily: Check instrumentation, severe errors, broken routes, and unexpected funnel discontinuities.
    • Weekly: Review segmented transitions, active experiments, onboarding evidence, routed accounts, and objections heard in customer conversations.
    • Monthly: Revalidate the adoption contract, intent-model weights, segment definitions, lifecycle ownership, and whether the core metric still represents customer value.

    Qualitative evidence belongs in this loop. Tag customer-call snippets by objection, compare the language used by progressing and stalled accounts, and connect those patterns to segment and product behavior. If customers repeatedly describe the problem differently from the landing page or sales narrative, change the promise or the targeting. If they accept the promise but stall at the same product event, change the experience.

    Assign one accountable owner to each transition, even when several functions contribute. Shared contribution is necessary; shared ambiguity is not. Marketing can own qualified arrival, product can own first and repeated value, sales can own assisted commercial progression, and customer success can own durable rollout. The precise boundaries can vary, but every stalled account should have an identifiable system owner.

    Key takeaways

    • Define adoption as repeated completion of a meaningful customer job within its natural usage cycle.
    • Separate acquisition, activation, adoption, retention, and expansion so one healthy metric does not conceal a broken transition.
    • Diagnose reactance, endowment, distance, uncertainty, or missing corroboration before choosing a product or GTM intervention.
    • Route accounts using fit, realized value, and complexity rather than treating all active users as sales-ready.
    • Measure product-led GTM with stable cohorts, behavioral retention, explicit guardrails, and experiments that end in a decision.

    At your next GTM review, leave with five things: one sentence defining adoption for one segment, one blocked transition, one barrier hypothesis, one intervention, and one owner with a decision date. If the meeting produces more campaigns and features but cannot produce those five decisions, the operating system is still organized around activity rather than adoption.

    References

  • The Leadership Operating System for a Scaling Organization

    The Leadership Operating System for a Scaling Organization

    Your organization rarely announces that it has outgrown its leadership model. The evidence arrives indirectly: routine decisions climb to executives, teams leave the same meeting with different interpretations, managers spend their time relaying updates, and choices that seemed settled keep reopening.

    A reorganization may move those problems, but it will not necessarily solve them. What you need is a leadership operating system: explicit agreements about roles, decisions, communication, learning, talent, and changes in leadership mode. Build those mechanisms before adding more hierarchy, and the organization can grow without making senior attention the dependency behind every important outcome.

    Diagnose the coordination failure before changing the org chart

    Start with a decision that recently consumed more leadership attention than it should have. Reconstruct its path from the moment the issue appeared to the moment someone finally acted. This exposes the operating gap more reliably than a broad discussion about communication or accountability.

    • What decision actually needed to be made?
    • Where did progress pause, and what was the team waiting for?
    • Who believed they owned the recommendation, the final choice, and the execution?
    • What context was missing when the issue reached leadership?
    • Which assumption or trade-off caused the decision to reopen?
    • Where can a future team find the rationale now?

    The answers usually point to a missing mechanism, not a lack of effort. Treat each recurring symptom as a diagnostic clue.

    What you noticeLikely operating gapFirst mechanism to install
    Routine choices repeatedly climb the hierarchyDecision boundaries are unclearA written map of who recommends, decides, contributes, and must be informed
    Teams agree on the work but explain its purpose differentlyContext is not traveling with the planA kickoff document that connects the problem, outcome, trade-offs, and ownership
    Settled choices keep getting relitigatedThe rationale and assumptions were not preservedA decision log with explicit conditions for reopening the choice
    The same failure appears in multiple initiativesLearning stops at the retrospectiveA searchable retrospective with named changes and owners
    Strong managers behave mainly as coordinatorsThe role rewards escalation more than judgmentA role contract that defines autonomous decisions and expected outcomes
    New leaders recreate basic practices from scratchOperating principles are implicitOutcome-based onboarding linked to documented principles and rituals

    Do not install every mechanism at once. Choose the recurring failure creating the most delay, risk, or executive dependency. Fix that loop, observe how behavior changes, and then move to the next constraint. Process earns its place by removing friction; it is not valuable merely because it looks disciplined.

    Design leadership roles from the next phase backward

    A scaling role changes before its title does. The product leader who once made most roadmap choices may later need to build a portfolio process, coach leaders who own those choices, and represent product trade-offs at the executive level. If the role holder continues succeeding through personal intervention, the organization gets a capable bottleneck instead of a scalable leader.

    Keep a future job description that looks 18 to 24 months ahead and is revisited quarterly. This is not a promotion plan. It is a forecast of what the organization will need from the role when its current methods stop working.

    Write a future-back role contract

    For each leadership role, document these fields in plain language:

    • Owned outcomes: the business, customer, or organizational changes for which this role is accountable.
    • Decision rights: choices the leader can make independently, choices that require consultation, and choices reserved for another role.
    • Systems to build: mechanisms that must keep working without the leader’s constant presence.
    • Interfaces: recurring decisions shared with product, engineering, sales, finance, people, or other functions.
    • Capabilities to develop: knowledge and judgment the next phase will demand.
    • Responsibilities to transfer: work the leader must stop owning, including the person or role being prepared to take it.
    • Failure signals: observable evidence that the role design or leadership approach is no longer sufficient.

    Review the contract quarterly with the role holder and the people most affected by it. Ask what remains correctly owned, what should move, and what new system must exist before the next phase begins. Waiting until performance visibly breaks turns a role-design problem into a personal performance crisis.

    Build cross-functional fluency before you need executive leverage

    Leadership at scale requires you to understand constraints outside your function well enough to make credible trade-offs. One practical example is the habit of reading two books about every peer executive’s area after joining a leadership team. The number is less important than the discipline: learn the economics, vocabulary, incentives, and failure modes behind your peers’ decisions.

    You can test your fluency during disagreement. Before defending your proposal, state the other function’s constraint in terms that its leader would accept. Then explain which trade-off you are asking the company to make. If you cannot do that, more authority will not repair the gap; you need more context.

    Succession belongs in the same conversation. A leader who develops a successor is not making the role less important. They are proving that the value of the role comes from judgment and system design rather than exclusive possession of information. That is what makes the person available for the next problem the company will need them to solve.

    Make decisions visible, then change leadership modes deliberately

    Decision quality does not scale when the real process lives in private conversations and executive memory. The organization needs a visible path from intent to choice to learning. That path should be lightweight enough to use under normal conditions and strong enough to support the team when risk rises.

    Use the kickoff as a contract, not a ceremony

    Every consequential initiative should begin with a written kickoff that answers the questions people otherwise discover halfway through execution:

    • What customer or business problem is being solved?
    • Why does it deserve attention now?
    • Which outcome should change, and how will the team recognize that change?
    • Who is the directly responsible individual for moving the initiative forward?
    • Who has final decision authority when trade-offs cannot be resolved?
    • What is deliberately outside the scope?
    • Which assumptions, dependencies, and risks could invalidate the plan?
    • Which decisions have already been made, and where is their rationale recorded?

    Do not confuse the directly responsible individual with the final decider. The first owns momentum and coordination; the second holds authority for a defined choice. Combining those concepts implicitly is a common reason teams either escalate everything or discover too late that approval never existed.

    Make the success measure an outcome, not evidence of activity. Shipping, launching, migrating, and holding a training session are outputs. The kickoff must state the change those outputs are intended to produce. If the team cannot express that change, it is not ready to defend the initiative’s priority.

    Separate debate, decision, and distribution

    A decision meeting should not be the first time participants encounter the problem. Send a concise pre-read containing the decision required, relevant constraints, viable options, evidence, and the recommendation. Use the meeting to challenge assumptions and resolve trade-offs. End it by recording the decision, owner, unresolved dissent, immediate implication, and any trigger that would justify reconsideration.

    The decision log is institutional memory, not an executive diary. A useful entry preserves:

    • the decision and the person authorized to make it;
    • the options considered and the reason one was selected;
    • the assumptions that mattered most;
    • the consequences for affected teams;
    • the condition that would cause the organization to revisit the decision; and
    • links to the kickoff, supporting material, and eventual retrospective.

    Use chat as an index into this system, not as its only memory. Give important channels an explicit purpose, consistent name, pinned index, and links to current kickoffs, decisions, and retrospectives. Summaries can live in chat; durable reasoning should remain searchable after the conversation scrolls away.

    Declare when the leadership mode changes

    Autonomy should be the normal mode, but it is not the only responsible mode. A customer incident, safety-critical launch, or brand-defining bet can justify a temporary period of closer senior involvement. The failure is not becoming hands-on. The failure is changing the rules without naming the change, its scope, or its end.

    When risk requires a different mode, write down:

    • the condition that triggered the change;
    • which decisions temporarily move to senior leadership;
    • which decisions remain with the team;
    • the communication and review cadence;
    • the outcome or risk threshold that permits normal autonomy to return; and
    • who is responsible for explicitly closing the temporary mode.

    This turns hands-on leadership into a bounded response rather than a permanent management habit. It also protects the team from learning the wrong lesson – that ownership disappears whenever stakes rise.

    During broader volatility, increase the frequency of useful context. Weekly communication can cover goals, financial runway, scenario changes, recent decisions, and the next three priorities. At an all-hands meeting, lead with the hard issue people are already discussing, explain the trade-offs, connect priorities to customer outcomes, allow unscripted Q&A, and publish the decisions afterward. Transparency is not the indiscriminate release of every unfinished thought. It is timely access to the context people need at the altitude where they can act.

    Build learning into culture, feedback, and the talent system

    A scaling organization cannot depend on leaders noticing every problem personally. It needs loops that detect weak signals, turn them into changes, and teach those changes to new people. Culture, feedback, retrospectives, hiring, and onboarding are parts of that same learning system.

    Treat cultural change as product work

    Culture becomes actionable when it is expressed as observable behavior. Instead of declaring that the organization needs more accountability, define the situation in which accountability currently fails, the behavior you want to see, and the mechanism that should make it easier.

    Use a simple sequence: write a precise problem statement, identify the desired behavior, run a limited pilot, choose evidence of adoption and impact in advance, and review what changed. This product-like approach to culture uses explicit goals and feedback loops rather than treating values as finished once they have been announced.

    Suppose important risks first appear after a product commitment has been made. A vague response would be to ask for better collaboration. A testable response would change the review ritual: circulate the decision material before commitment, require affected functions to record risks in the same place, and observe whether consequential objections now surface while the decision is still reversible. That gives you behavior to inspect instead of sentiment to debate.

    Give high performers developmental tension

    Strong performance often attracts praise while reducing the amount of corrective feedback a person receives. That is a poor bargain. A leader can be delivering excellent results while relying on habits that will fail at the next level of scale.

    Make development a recurring part of one-to-ones for every performer. Ask:

    • Which behavior is creating disproportionate value right now?
    • Where could the same strength become limiting as the role expands?
    • What specific event or observation supports that view?
    • What should the person try before the next check-in?
    • What support or feedback does the manager need to provide?

    Require evidence and examples, not personality labels. Add upward feedback so managers experience the same standard they ask others to accept. When a leader feels certain about an interpretation, have them write the opposite hypothesis and identify evidence that could support it. This interrupts premature certainty without turning every decision into endless debate.

    Close initiatives with a structured, searchable retrospective. Record the intended outcome, actual result, useful choices, failed assumptions, deviations from the kickoff, and changes the team will make. Give each change an owner and connect it to the next relevant kickoff or operating-principle review. A lesson without a destination is documentation, not organizational learning.

    Make talent decisions produce comparable evidence

    Hiring becomes less reliable as role ambiguity grows. Executive polish, employer brands, and familiar career patterns can look like signal when the organization has not defined what success means. Write the role scorecard before meeting candidates. Anchor it in outcomes, essential competencies, and observable behaviors rather than resume proxies.

    Then make the evaluation process consistent:

    • Ask candidates to reconstruct real ambiguous decisions, including constraints, assumptions, disconfirming evidence, trade-offs, and measurable results.
    • Use consistent core prompts so different candidates generate comparable evidence.
    • Have interviewers score independently before discussing the candidate.
    • In the debrief, connect every claim to the scorecard and have the most senior participant speak last.
    • Use reference checks to test observed behavior, especially collaboration and judgment under pressure.
    • For an executive role, clarify the mandate and decision rights as rigorously as the candidate’s capabilities.

    Onboarding should continue the same logic. A 30-60-90 plan needs explicit outcomes, purposeful shadowing, and early relationship-building across functions. Give the new leader the operating principles, active decision logs, recent retrospectives, and future role contract. If onboarding teaches only current projects, the person learns the workload but not the system that gives the work meaning.

    Finally, connect your principles to the full talent lifecycle. The same observable behaviors should appear in hiring rubrics, onboarding, one-to-ones, performance conversations, and product or operating reviews. A principle scales when people repeatedly use it to make choices; repetition on a values page does not count.

    Key takeaways: install a minimum viable leadership system

    • Trace a real stalled or reopened decision before assuming the answer is a reorganization.
    • Define leadership roles through owned outcomes, decision rights, systems to build, interfaces, and responsibilities to transfer.
    • Maintain a future job description so leaders prepare for the role the next phase requires.
    • Connect every consequential initiative through a kickoff, decision log, written communication, and searchable retrospective.
    • Make autonomy the default, but declare the scope and exit conditions whenever risk requires a more hands-on mode.
    • Treat culture as observable behavior that can be piloted, measured, reviewed, and changed.
    • Use structured hiring and onboarding to preserve standards without relying on pedigree, charisma, or organizational folklore.
    • Judge every new ritual by whether it improves decisions, distributes context, or converts experience into reusable learning.

    Start with one operating cycle

    At your next leadership meeting, bring one decision that required repeated escalation. Trace where it failed, choose the smallest missing mechanism, name its owner, and attach it to an existing cadence. Run the full loop through decision and retrospective before adding another process.

    At the end of the cycle, ask whether the decision boundary became clearer, whether the rationale reached affected teams, and whether the learning changed subsequent work. Keep the mechanism if it changes behavior. Revise or remove it if people maintain the artifact without using it to decide.

    The practical test of a leadership system is simple: sound decisions and useful context should travel farther than any individual leader can. Build that capability one recurring failure at a time, and growth becomes less dependent on heroic attention from the top.

    References

  • Startup Validation: A Practical Path to Product-Market Fit

    Startup Validation: A Practical Path to Product-Market Fit

    You don’t need more evidence that your market is large. You need evidence that a specific customer has a painful job, recognizes your promise, changes behavior to try your solution, and keeps using it after the novelty is gone.

    Those are separate tests. Startup teams get into trouble when they compress them into one vague question: Does this idea have potential? A yes at one stage does not carry forward automatically. By collecting evidence in the right order, you can tell whether to sharpen the message, change the product, narrow the customer, or begin scaling.

    Treat validation as a chain of evidence

    Product-market fit is not the first thing you validate. It sits at the end of a chain. Each link answers a different question and requires a different kind of evidence.

    1. Problem evidence: Does a defined customer encounter this problem in a real workflow? Look for recent examples, consequences, workarounds, and a recognizable trigger.
    2. Language-market evidence: Does that customer immediately understand the promise and see it as relevant? Landing-page responses, demo requests, and consistent customer language can help answer this.
    3. Solution evidence: Can the customer reach the promised outcome with the product? Activation, time-to-first-value, workflow adoption, and willingness to invest effort matter here.
    4. Product-market evidence: Does value persist? Retention, repeat use, referrals, expansion, and sustainable revenue indicate that the relationship is becoming durable.

    A waitlist validates interest in a promise. It does not validate delivery of that promise. A successful pilot validates value in a controlled setting. It does not prove that acquisition, onboarding, and retention will work repeatedly across a market.

    X1’s 600,000-person waitlist demonstrated exceptional consumer interest and narrative resonance. The remaining PMF questions still concerned waitlist conversion, activation, engagement, retention, and organic growth. Retool’s $2 million in annual recurring revenue before its public launch represented a different level of commitment: customers had crossed from attention into payment. Neither figure is a benchmark your startup must match. The useful distinction is the kind of uncertainty each signal removes.

    Use the chain as a set of decision gates. If problem evidence is weak, more product work is premature. If the problem is strong but response to the message is weak, revisit positioning. If signups are strong but activation is poor, compare the promise with the first product experience. If customers activate but do not return on the natural cadence of the job, investigate whether the value is durable before buying more traffic.

    Start narrow enough to hear a reliable pattern

    An early ideal customer profile should be narrow enough that the people inside it share a job, context, trigger, and meaningful constraint. Industry and company size alone rarely provide that precision.

    A useful hypothesis fits into one sentence: A specific user in a specific context needs to complete a specific job when a recognizable trigger occurs, but a constraint makes the current approach costly or unreliable.

    For example, developers building internal tools are more coherent as an initial audience than everyone who builds software. Freelance designers trying to publish production websites are more coherent than everyone who needs a website. Narrowing the profile lets you detect repeated behavior instead of averaging incompatible feedback.

    Run interviews as investigations of past behavior, not auditions for your idea. Select people who have encountered the job recently, own some part of its consequence, and can show or describe their current workflow. A friendly person with an opinion is less useful than a skeptical person with a real workaround.

    1. Define the learning goal before the call. Write down what you need to learn, what evidence would weaken your belief, and which decision the answer will affect.
    2. Anchor the conversation in a recent event. Ask the customer to reconstruct what happened rather than predict what might happen in an imagined future.
    3. Synthesize immediately. Separate observed behavior from interpretation while the details are fresh, then compare patterns only within the same ICP and job.

    Questions that expose useful evidence include:

    • Tell me about the last time you had to complete this job.
    • What triggered the work?
    • Walk me through what you did, including the tools and people involved.
    • Where did the process slow down, fail, or require rework?
    • What happened because of that friction?
    • What workaround have you already tried?
    • How did you decide whether the problem was worth fixing?
    • Who else cared about the outcome or had to approve a change?
    • What happened next?

    Avoid asking whether someone likes the idea, whether they would use it, or which features they want. Those questions invite politeness and speculation. A requested feature is still useful, but only as the beginning of root-cause analysis. Trace it back through the underlying job, the triggering situation, the current workaround, and the consequence. That is how you distinguish a reusable problem from one customer’s preferred implementation.

    After each interview, record the customer’s context, trigger, workflow, workaround, consequence, decision process, commitment, and exact vocabulary. Also record contradictory evidence. If a pattern appears only after combining unrelated roles or use cases, you have not found a pattern; you have hidden segmentation inside an average.

    There is an important complication when the market is still forming. Vanta began pursuing SOC-2 compliance for startups in 2018, before many startups treated it as a requirement. Interviews about current demand alone could have understated the opportunity. In an emerging market, test the trajectory as well as the present pain: identify the earliest buyers who already feel the constraint, the event that makes it urgent, and the conditions under which others will follow. Strategic conviction should produce a falsifiable market thesis, not permission to ignore contrary evidence.

    Ask the market to spend something before you build broadly

    Compliments are cheap. Validation becomes stronger when a prospective customer gives up something scarce: attention, time, workflow access, reputation, data, or money. The appropriate commitment depends on the product and buying process, but the direction should move from passive interest toward consequential action.

    1. Attention: The person stops, clicks, or reads.
    2. Declared interest: The person joins a waitlist, replies, or requests a demonstration.
    3. Effort: The person completes an interview, shares a workflow, or returns for another session.
    4. Access: A design partner supplies representative data, involves colleagues, or makes room for implementation.
    5. Economic commitment: The customer enters a paid pilot, signs a contract, or completes the real purchasing process.
    6. Continuing commitment: The customer renews, expands, refers a peer, or repeatedly returns to the product.

    This is not a universal funnel. An enterprise prospect may need security and procurement reviews before payment is possible. A consumer may reveal commitment through repeated voluntary behavior long before paying. The point is to request the strongest honest action that fits the current stage instead of treating positive words as equivalent to behavior.

    You can test the narrative before building the full product. Write a landing-page promise that names the target customer, the triggering problem, the desired outcome, and the reason your approach is different. Pair it with a call to action that measures the next real commitment. A vague request to learn more produces vague evidence; a request to share a workflow, schedule an implementation discussion, or join a defined pilot reveals more.

    For a B2B startup, founder-led sales should double as product discovery. After a demonstration, ask which existing workflow the product would replace, who must approve the change, what implementation or security constraints could block adoption, and what must be true for a pilot to begin. A scheduled next step with the right stakeholders is stronger evidence than an enthusiastic closing comment.

    For a consumer startup, branding, positioning, referrals, and scarcity can establish emotional resonance and distribution potential. They cannot tell you whether the product creates a habit or a recurring outcome. Track how many interested people activate, what meaningful action they complete, whether they return when the need recurs, and whether they invite others after experiencing value.

    Do not scale acquisition while most prospects stop at the weakest commitments. Diagnose the break first. If people click but do not sign up, the promise or targeting may be wrong. If they sign up but avoid setup, the expected benefit may not justify the effort. If they complete setup but never reach value, the product or onboarding is failing. More traffic will increase the volume of the same unresolved problem.

    Turn design partners into a weekly evidence loop

    A design partner is not simply an early customer who can request features. The best partners fit the same narrow ICP, face an active problem, expose the real workflow, respond quickly, and have a credible path to adoption. Their role is to help you find a repeatable solution, not fund a collection of unrelated custom projects.

    Use one operating cadence from discovery through delivery

    A lightweight weekly cadence keeps conversations, product changes, and behavioral evidence connected:

    1. Choose the riskiest assumption. At the start of the week, name the belief that matters most to the next decision. Frame it around a customer outcome rather than a feature.
    2. Observe the current workflow. Watch the partner attempt the job or reconstruct a recent attempt. Capture tools, handoffs, constraints, and failure points before discussing solutions.
    3. Ship the smallest reusable improvement. Prefer a change that tests the underlying job across the target segment over a bespoke implementation for one account.
    4. Measure the value path. Connect qualitative observations to activation, time-to-first-value, repeat use, referrals, and commercial progress.
    5. Write a decision. At the end of the week, state whether the evidence supports continuing, adjusting the hypothesis, narrowing the ICP, or stopping that line of work.

    Keep a one-page evidence log for each design partner. Record the triggering event, the first-value action, elapsed time to that action, blockers, the expected return event, observed return behavior, stakeholders involved, and the next commercial commitment. This makes it harder for a memorable conversation to outweigh actual product behavior.

    Treat documentation, templates, examples, and implementation support as part of the value path. This is especially important for technical products. A user who understands the primitives but cannot assemble them into a working outcome has not activated. Improving the example or setup path can reduce time-to-value more than adding another capability.

    Feature requests need the same discipline. Map each request through five questions: What job is the customer trying to complete? What triggers it? What do they do now? What is the consequence of the current approach? How many customers in the same target segment encounter the underlying problem? A loud customer is not automatically a market, and several similarly worded requests can still represent different jobs.

    Retool’s early developer focus illustrates why this loop compounds. Tight collaboration with early customers, rapid delivery, and attention to developer-facing language reduced friction across discovery, onboarding, and activation. Webflow followed the same strategic shape from a different starting point: depth with designers came before broad adoption. In both cases, expansion was earned by solving a coherent user’s job well enough that the product could travel beyond its initial wedge.

    Scale only after pull survives the launch

    A launch changes who is paying attention. It does not necessarily change the value of the product. Review launch cohorts separately from later cohorts so a concentrated group of enthusiasts does not hide weaker behavior among ordinary customers.

    What you observeWhat it may meanWhat to do next
    People join the waitlist or start signup but do not activateThe story is stronger than the product experience, setup cost, or targetingCompare the promise with the first session and remove the earliest value-path blocker before adding traffic
    Customers activate but do not returnFirst-run value is not durable, or you are measuring on the wrong cadenceIdentify the natural return trigger for the job and investigate what customers do when it occurs again
    The core ICP retains while adjacent segments do notYou may have a valuable wedge rather than a broad marketDeepen the core workflow and resist premature expansion
    Retained customers refer peers, renew, or expandValue is beginning to generate organic and commercial pullTest whether new cohorts from repeatable channels show similar behavior
    The launch cohort performs well but later cohorts weakenThe initial audience or channel may have produced an unusually favorable sampleReproduce acquisition and retention with less concentrated cohorts before increasing spend
    Demand rises but every implementation requires founder interventionCustomer value may be real while delivery remains operationally fragileProductize the repeated implementation steps before accelerating acquisition

    There is no single metric that declares product-market fit across consumer products, developer tools, and enterprise software. Measure behavior on the cadence of the job. A product used when a periodic event occurs should not be judged as though its value requires daily use. A B2B product may show pull through recurring usage, renewal, account expansion, and champion-led referrals. A consumer product may show it through retained engagement, habit, word of mouth, and an organic referral loop.

    The strongest PMF case triangulates three forms of evidence: customers describe an important job and recognizable consequence; behavioral data shows that they reach and repeat value; commercial or organic behavior shows that the product can grow without constant persuasion. Fundraising, press attention, a viral launch, and a large top-of-funnel number can support the company, but none substitutes for that combination.

    Vanta’s decision to rely heavily on word of mouth and wait until it had hundreds of customers before building a proper website is a useful expression of this principle. The company prioritized customer outcomes and retained demand before investing heavily in its public top of funnel. You do not need to copy that tactic. You do need to know whether growth is amplifying demonstrated value or merely increasing exposure.

    Key takeaways

    • Validate in sequence: problem, language, solution, and durable pull.
    • Define an ICP around a shared job, trigger, context, and constraint, not broad demographics alone.
    • Use interviews to reconstruct recent behavior and workarounds, not collect opinions about your idea.
    • Ask prospects for progressively stronger commitments that fit the product and buying process.
    • Run design partners through a weekly loop connecting observation, delivery, measurement, and a written decision.
    • Scale only when retention, repeat use, referrals, renewal, or expansion survive beyond the initial launch audience.

    Before your next roadmap meeting, place every piece of evidence under the four validation gates. Circle the first gate that remains weak. Give the team one week to strengthen or disprove it, and postpone every proposed feature that does not help answer that question.

    References

    • Shivam.Consulting Blog – How Retool Hit $2M ARR Pre-Launch: My Playbook on Developer Focus, Product-Market Fit, and GTM
    • Shivam.Consulting Blog – Inside X1’s Pivot: The Playbook Behind a 600K Waitlist and a $15 Million Raise
    • Shivam.Consulting Blog – From Narrow ICP to Broad Adoption: Customer Empathy That Fueled Webflow’s PMF
    • Shivam.Consulting Blog – From Doubt to Dominance: Vanta’s Bold Bet on Startup Security and Product-Market Fit
    • Shivam.Consulting Blog – Validate Your Startup Idea Fast: My Early User Research Playbook for High-Quality Interviews
  • From IC to Manager: Proven Strategies to Avoid Pitfalls and Lead High-Impact Teams

    From IC to Manager: Proven Strategies to Avoid Pitfalls and Lead High-Impact Teams

    The leap from individual contributor to manager looks straightforward on paper, yet it’s one of the trickiest transitions I’ve seen in high-growth environments. In my role at HighLevel, I’ve watched brilliant engineers stumble when the job changes from building the product to building the people who build the product. The difference isn’t incremental—it’s a complete shift in identity, incentives, and daily habits.

    Most startups get it wrong because they promote for technical excellence and throughput, then keep the new manager doing their old job with “a little people stuff on the side.” That’s a recipe for burnout and underperformance. The first principle is simple: management is a different job. Success is no longer measured by your code, but by your team’s clarity, velocity, and outcomes.

    Set expectations and goals with precision on day one. I establish a clear role charter, spell out decision rights, and align to outcomes vs output OKRs so the new manager understands what “great” looks like. We define a 30/60/90 plan that includes team health metrics, delivery goals, and collaboration routines with product and design. The aim isn’t to ship more tickets—it’s to reliably ship the right outcomes.

    To turbocharge a team’s effectiveness, I focus on operating cadence and flow. That means crisp intake, visible priorities, lean WIP, tight feedback loops, and regular retros that drive real change. I remove systemic blockers, protect focus time, and make psychological safety a non-negotiable. When people feel safe, they surface risks early, challenge assumptions, and accelerate learning.

    High-impact feedback is fast, frequent, kind, and specific. I coach managers to use situation–behavior–impact, to separate people from problems, and to balance reinforcing and redirecting feedback. Written summaries after key conversations prevent drift, while short feedback cycles create compounding growth. Recognition is not an afterthought—it’s a performance tool.

    Going from peer to manager requires an explicit reset. I encourage managers to communicate the new expectations, re-establish boundaries, and commit to fairness over familiarity. This includes confidential 1:1s, transparent decision-making, and a clear stance on performance bars. Trust grows when people experience consistency, not when they hear platitudes.

    Delaying action on low performance is one of the most costly leadership mistakes. It silently taxes your top performers, normalizes mediocrity, and corrodes culture. Diagnose if the issue is skill or will, offer targeted support with time-bound milestones, and be decisive. Managing someone out can be both humane and necessary—clarity and dignity can coexist.

    For first-time managers, I use a simple playbook. In the first 30 days, run a listening tour and baseline the team’s delivery, quality, and morale. By day 60, implement the new operating cadence, align on outcomes vs output OKRs, and tighten cross-functional rituals. By day 90, complete career conversations, calibrate performance, and publish a team charter that codifies how you plan, build, and learn.

    The throughline in all of this is ownership: own the outcomes, the culture, and the system. When you make the mindset shift from doing the work to enabling the work, you’ll find that the manager role is not a detour from impact—it’s a force multiplier. With clear expectations, disciplined execution, and courageous feedback, you’ll transform a promotion into a platform for sustained, compounding results.

    Book a consult png image
  • Scale Beyond One Product: Battle‑Tested Tactics for Ideas, Teams, and Product Reviews

    Scale Beyond One Product: Battle‑Tested Tactics for Ideas, Teams, and Product Reviews

    Expanding from a single hero product to a resilient multi‑product portfolio is one of the most consequential moves a SaaS company can make. I’ve navigated this shift firsthand and studied how leaders approached it at companies like Stripe and Watershed. What follows is the playbook I use to assess new product ideas, structure teams for 0‑1 execution, and run rigorous product reviews without losing momentum on the core business.

    I start by clarifying the type of multi‑product strategy we’re pursuing. Are we building adjacent features that deepen adoption, launching true net‑new products for new buyers, extending a platform with new primitives, or assembling a bundle that compounds customer value? That choice dictates everything else—resource allocation, hiring profiles, team topology, and the shape of our product discovery.

    Stories from Stripe’s multi‑product success reinforce a principle I believe deeply: launch with small, high‑trust teams and a brutally clear problem statement, then iterate fast with real customers. When adding products like Stripe Billing and Stripe Treasury, the work required not only great execution but also adapting to new buyer profiles and purchasing motions. The lesson I apply is simple—don’t assume the new buyer is just a variant of the old one.

    Resource allocation is where strategy meets courage. I protect the core product’s roadmap while ring‑fencing a few exceptional builders to pursue secondary bets. These squads operate with clear, outcome‑based goals and tight feedback loops, not sprawling OKR spreadsheets. The aim is to make small, reversible bets at first, then scale conviction with evidence—market pull, repeatable use cases, and early revenue signals.

    Team structure matters even more than headcount. I form new‑product squads that behave like a startup within the company—full‑stack ownership, minimal dependencies, and direct access to customers. The early team must combine product discovery instincts with the ability to ship. Great early‑stage product thinkers show crisp problem framing, a bias for learning, and the humility to change course. One common fail‑case I watch for is hiring purely for potential over demonstrated ability to drive ambiguous work from zero to one.

    Hiring the right people for 0‑1 work is its own craft. I look for signals of self‑direction, obsession with customer outcomes, and the ability to reason from first principles under uncertainty. I use five interview questions to unearth hidden talent among product candidates, all designed to reveal how they validate problems, reduce scope intelligently, earn trust with engineers, and handle the uncomfortable middle of product discovery.

    Even the best teams stumble when product, packaging, and go‑to‑market are misaligned. I’ve seen what happens when an organization assumes the existing buyer will adopt the new product in the same way—pricing misses the mark, activation drops, and sales enablement lags. The fix is to revisit the buyer, refine the value proposition, and rebuild the path to value so the first‑run experience matches the new buying journey.

    To keep new bets honest, I treat them with “definite optimism”—a clear, written view of what success looks like and a pragmatic path to get there. I focus on the sequence of proof: problem validation, consistent user pull, and evidence of repeatable adoption. In a new or early market, I combine a methodical approach (milestones, stages of validation) with analytical rigor (leading indicators, customer expansion patterns) to decide which products to prioritize and when to scale.

    Goal‑setting for new products must be measurable yet forgiving of discovery. I favor outcome‑centric checkpoints over vanity metrics, and I evaluate bets by expected learning speed and cost of delay. This keeps us moving fast without confusing activity for progress.

    My product reviews are anchored by 12 questions that force clarity on problem, user, value, and risk. I often share these questions as a pre‑read so teams can self‑diagnose and come in focused on decisions rather than updates. “The Enterprise Rent‑A‑Car Story” is a helpful reminder for me that distribution and execution are as decisive as the product idea itself. When building for net‑new‑customers, I re‑focus the questions on buyer change, activation friction, and early‑life cycle signals.

    User feedback is the lifeblood of 0‑1. I collect inputs across interviews, product analytics, and support tickets, but I interpret them through the lens of the problem statement rather than raw feature requests. Product development must start with problem validation; otherwise, speed becomes a liability and discovery masquerades as delivery.

    For ongoing inspiration and sharp thinking in product management leadership and product discovery, I regularly revisit a few resources. First Round Capital’s Newsletter: https://review.firstround.com/newsletter. The ‘Wins Above Replacement’ metaphor: https://en.as.com/mlb/wins-above-replacement-war-baseball-statistic-explained-n/. Zero to One by Peter Thiel & Blake Masters: https://www.amazon.com.au/Zero-One-Notes-Startups-Future/dp/0804139296.

    When I look across the ecosystem—Atlassian: https://www.atlassian.com/, Cash App: https://cash.app/, Figma: https://www.figma.com/, First Round Capital: https://firstround.com/, Lattice: https://lattice.com/, Notion: https://www.notion.so/, Paypal: https://www.paypal.com/, Stripe: https://stripe.com/, Watershed: https://watershed.com/—I see variations of the same pattern: disciplined product discovery, sharp resource allocation, and product review rituals that reward learning over laddered status updates.

    I also learn from builders who think in systems and act with urgency. Jack Dorsey: https://twitter.com/jack. Patrick Collison: https://twitter.com/patrickc. Shreyas Doshi: https://twitter.com/shreyas. Their public writing on product strategy, execution, and outcomes vs output informs how I evaluate talent, decide what not to build, and keep teams aligned as we scale beyond one product.

    Book a consult png image
  • Scaling With Heart: Self-Aware Leadership, Tough Calls, and 10x Team Performance

    Scaling With Heart: Self-Aware Leadership, Tough Calls, and 10x Team Performance

    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.

    Book a consult png image
  • My playbook: Intuition vs data, big swings, and product-led growth lessons from Slack

    My playbook: Intuition vs data, big swings, and product-led growth lessons from Slack

    I get asked constantly how I decide when to trust my gut, when to lean on data, and when to take a big swing versus iterate. As a product leader, my answer has been shaped by hard-won lessons building B2B SaaS, product-led funnels, and enterprise features. Recently, I revisited Slack’s approach to decision-making, product reviews, and balancing product-led vs sales-led growth—and distilled a set of practices I use with my teams today.

    Noah Desai Weiss is the Chief Product Officer of Slack, and has an accomplished track record inside and outside of the company. He started Slack’s Search, Learning, and Intelligence division, led the Self-Service (SMB) Business, and led the Expansion and Virtual HQ product areas (responsible for Huddles, Clips, and more). Before joining Slack, Noah was the SVP of Product Management at Foursquare (raised over $390m), and was a Product Manager at Google.

    The throughline for me starts with a simple truth: not all decisions should be data-driven. Early in a product’s life—or when exploring a novel experience—data is often either unavailable or misleading. That’s where intuition, taste, and judgment come in. I treat intuition as a hypothesis generator and momentum maker, then instrument quickly to validate direction. This blend of “When to use intuition vs data to drive decisions” has saved me from overfitting to small datasets and from analysis paralysis when speed was the real advantage.

    I’ve learned that “Taste and judgment are learnable.” You can coach it. Review artifacts together. Run side-by-side comparisons of design explorations. Write down what “good” looks like and why. My teams keep a living gallery of exemplary UX patterns and empty-state copy that exemplifies our bar. Over time, this scales the craft of intuition across a larger org—just as “How Slack scales intuition across their product org” suggests.

    Of course, there are “Challenges of intuition-led product building.” The biggest are founder or leader overreach and survivorship bias. I mitigate this with timeboxed discovery: we commit to a clear decision date, capture our priors in writing, and express our confidence as a range rather than a point estimate. This sets up a healthy dynamic for “Managing pace vs accuracy in decision-making.” We move fast when reversibility is high, we move slower when the blast radius is large.

    Matching people to the work matters too. Some product problems are inherently ambiguous and benefit from researchers, designers, and PMs who derive energy from the unknown. Others are best led by optimization-oriented builders who light up when the metric moves. I’m explicit about “Matching people to data vs intuition-driven work,” and I rotate folks so they can build both muscles.

    In remote and hybrid environments, I’ve found the most underrated traits are proactive context-sharing, crisp written communication, and the ability to create signal in Slack and docs. “Underrated qualities for remote workers” aren’t just stylistic preferences—they are execution speed ups. I look for people who make everyone around them smarter asynchronously.

    On product process, I’m inspired by “How Slack runs product reviews.” My rubric: one problem statement, a tight narrative memo, the bet framing (assumptions, risks, kill criteria), and outcomes tied to “outcomes vs output OKRs.” We align on the decision owner, consent vs consensus, and the next irreversible checkpoint. This keeps reviews from becoming theater and pushes decisions to the right altitude.

    Culture shows up in small moments. “The importance of a team’s ‘vibe’” is tangible: Do we demo early? Do we celebrate learned negatives as much as wins? Do engineers, designers, and PMs feel joint ownership of the experience, not just their function’s slice? When the vibe is right, latency from idea to insight collapses—and that compounding is everything in product discovery.

    Portfolio balance matters. I aim for a mix that lets us keep shipping customer-visible improvements while reserving room for breakthroughs. “Balancing “big swings” with incremental improvements” requires explicit ring-fencing: 70/20/10 works well for many orgs. Big swings get stage gates and PR/FAQ-like artifacts; incremental bets get weekly ship cadence and tight measurement. When we miss, we run pre-mortems and decision journals, reinforcing “Rituals for good decision-making.”

    Go-to-market is where strategy meets friction. My guidance on “Advice on product-led vs sales-led growth” is to design the handshake up front. Let product-led growth do the land—self-serve activation, collaborative aha, bottoms-up virality—and let sales-led growth do the expand—security, compliance, procurement, multi-workspace governance. Instrument the handoffs, define eligibility heuristics, and ensure pricing doesn’t punish adoption. This is also where “Which products should focus on end-users versus executives” gets real; optimize early journeys for end-user success while giving executives the portfolio-level control and analytics they require.

    I’m continually impressed by “What Slack learns from Salesforce.” Enterprise trust, admin controls, and scalable GTM motions can coexist with consumer-grade product craft. That hybrid DNA is powerful. I’ve adopted similar patterns: build for end-user joy, layer enterprise-grade controls, and price to match value realization, not procurement theatrics.

    Speaking of pricing, “Pricing lessons from Salesforce and Marc Andreessen” pushed me to keep pricing simple enough for PLG while being flexible enough for enterprise. Seat-based pricing remains intuitive for collaboration products, but usage and “SaaS pricing” add-ons can map value to heavy features without overcrowding your price page. The key is to test willingness to pay early, avoid grandfathering yourself into a corner, and treat packaging changes like product changes—with discovery, rollout plans, and success metrics.

    Humility isn’t fluffy—it’s an execution advantage. “Slack’s humility and why it matters” resonates with how I try to lead: ruthlessly honest about what we don’t know, eager to learn from customers quickly, and unafraid to reverse course when the evidence changes. That humility turns into speed because we stop defending past decisions and start iterating toward truth.

    When working with a strong product voice at the top, “How to build product with a product-focussed founder” comes down to mutually agreed principles. Capture the founder’s taste in explicit heuristics, define the moments where their judgment should overrule the process, and codify how dissent and disagree-and-commit work in practice. This protects clarity without stifling creativity.

    Here are the topics I unpacked and continue to apply across teams: “When to use intuition vs data to drive decisions,” “The most underrated traits in a remote work environment,” “How Slack runs product reviews,” “The importance of a team’s ‘vibe’,” “Managing pace vs accuracy in decision-making,” “Balancing “big swings” with incremental improvements,” and “Advice on product-led vs sales-led growth.” Each one is a lever that compounds when used together.

    Curious to learn more about Slack? You can try Slack Pro and get 50% off using this link.

    Creative Selection – Inside Apple’s Design Process During the Golden Age of Steve Jobs: https://www.amazon.com/Creative-Selection-Inside-Apples-Process/dp/1250194466

    Salesforce acquires Slack: https://slack.com/blog/news/salesforce-completes-acquisition-of-slack

    Thinking in Bets – Making Smarter Decisions When You Don’t Have All the Facts: https://www.amazon.com/Thinking-Bets-Making-Smarter-Decisions-ebook/dp/B074DG9LQF

    Book a consult png image
  • Hard-Earned Lessons from Loom: Product Strategy, Alignment at Scale, and Hiring That Wins

    Hard-Earned Lessons from Loom: Product Strategy, Alignment at Scale, and Hiring That Wins

    I’m always looking for crisp, scalable ways to drive product strategy, organizational alignment, and cross-functional performance that actually ship outcomes. Studying Loom’s operating system—and the career arc behind it—offered a masterclass worth sharing. Anique Drumright is the COO at Loom, a video communication tool for streamlining workflows. Loom has raised over $200M, and was last valued at $1.5B. Anique has a proven track record across product development, executive leadership, and building high-performing organizations. Before joining Loom, Anique was the VP of Product at TripActions, where she scaled the team over 8x globally, and she has also held multiple roles at Uber. In this breakdown, I dig into best-practice product management, how to achieve alignment at scale, the mechanics of cross-functional performance, Anique’s approach to finding top organizational talent, how to hire for roles outside your area of expertise, the most common fail cases with internal and external recruitment, and the specific interview tactics that actually surface the truth. One theme I return to often is the transition from product management to executive leadership. As a PM, I optimize for customer insight, prioritization, and execution velocity. As an exec, I optimize for clarity, systems, and sustained energy across teams. The job shifts from owning a roadmap to owning the conditions under which many roadmaps thrive—organizing for outcomes, setting non-negotiable standards, and removing ambiguity. Storytelling sits at the center of launch excellence. I love how Loom anchors launches in a human narrative: define the painful “before,” demonstrate the transformative “after,” and spotlight one memorable capability that makes the switch inevitable. I pair this with a crisp narrative memo, a demo-first internal review, and a simple, outcome-oriented success metric—so product, marketing, and sales sing the same chorus. Managing cross-functional scope and performance requires ruthless role clarity and shared measures of success. I align on a single definition of the customer problem, agree on leading indicators we can move now, and assign one DRI per decision. When we use outcomes vs output OKRs, we unlock better trade-offs: fewer features shipped, more customer problems solved. Organizational alignment is both essential and fragile. What looks like misalignment is usually mismatched time horizons, unclear ownership, or different definitions of success. The antidote is explicit agreements: who decides, how we decide, and what “good” looks like this quarter. When in doubt, I over-communicate context, not tasks. I’ve seen at scale—Uber is a notable example—that alignment travels fastest through shared rituals, not longer documents. Weekly business reviews, lightweight decision logs, and a common operating cadence create a heartbeat the org can follow. The point isn’t ceremony; it’s repeatable clarity. My go-to alignment rituals are simple. A Monday priorities memo sets the narrative and the week’s must-win outcomes. Midweek, a cross-functional stand-up surfaces risks and unblocks dependencies. Friday, we close the loop with a red-yellow-green on outcomes and a short retro on decisions—not just results—so we compound learning. One-on-ones are performance multipliers when they’re designed well. My winning format: start with energy and focus (what’s giving or draining energy), review outcomes not activity, walk a single thorny decision to closure, and end with explicit asks in both directions. Over time, this builds trust and speed. When and how to help functional leaders matters. I jump in when a decision is high-impact and ambiguous, when speed has stalled, or when the problem crosses multiple functions. Otherwise, I coach on principles and expect leaders to own the path. If I’m often in the weeds, we have a structure or talent gap—not a diligence problem. Hiring outside my domain expertise starts with outcomes, not resumes. I write the first-90-day outcomes, name the decisions the role must own, and recruit with a structured case that mirrors the real job. I bring in a domain advisor to probe depth and run a work-sample test to reduce false positives from polished storytellers. For senior leaders, my favorite interview questions are simple and hard to fake: Tell me about the last time you changed your mind on a critical decision—what evidence moved you? Walk me through your operating cadence—meetings, artifacts, and decisions—in a typical month. Describe your hardest cross-functional miss and the system you changed to prevent a repeat. The specificity of answers reveals the operator from the commentator. I adjust the hiring process when I’m outside my depth: heavier emphasis on work samples, more structured rubrics, a domain expert panel, and reference checks that test for actual outcomes. When the role is pivotal, I’ll run a paid trial project with clear guardrails; reality is the best filter. Common patterns of failed external hires: they manage optics over outcomes, never rewire the system, and don’t create leaders beneath them. Failed internal promotions often show up as scope growing faster than judgment, a reluctance to reset standards with former peers, or success limited to a familiar domain. Avoid over-promotion by decoupling recognition from scope; celebrate excellence without inflating title or span prematurely. To get honest answers in interviews, I normalize candor and ask for receipts. I request artifacts—planning docs, dashboards, postmortems—and I probe for the counterfactual: what would you do differently if you had to do it again? In reference checks, I ask for moments of truth: the hardest feedback you gave them, a decision you disagreed with and how they handled it, and the exact conditions under which you would rehire them tomorrow. Sustaining energy is an executive’s quiet superpower. I watch team energy levels as closely as metrics. What inspires people in a company is progress they can feel, standards that mean something, and leaders who tell the truth. If we keep those three alive, performance follows. A month in the life of a COO (and frankly any executive operator) is a portfolio: setting the narrative and outcomes, running the operating cadence, calibrating talent, and clearing systemic blockers. The best leadership dynamics work because roles are explicit, trust is earned through delivery, and debates resolve into single-threaded ownership—not committee compromises. Resources for further exploration: Loom (https://www.loom.com/), Navan (formerly TripActions): https://navan.com/, Teach for America: https://www.teachforamerica.org/, Uber: https://www.uber.com/. Timestamps I mapped my notes to for quick scanning: [00:03:00] similarities and differences between PM and executive leadership roles; [00:06:53] storytelling in launches; [00:10:01] cross-functional scope and performance; [00:13:41] goal-setting with functional leads; [00:16:59] organizational alignment; [00:20:40] alignment at scale; [00:24:06] alignment rituals; [00:25:23] one-on-one format; [00:27:49] supporting functional leads; [00:29:13] hiring outside your expertise; [00:32:55] interview questions; [00:33:55] adapting the hiring process; [00:36:09] failed external hires; [00:37:40] failed internal hires; [00:39:05] avoiding over-promotion; [00:40:51] inspiration; [00:45:40] getting honest answers; [00:47:12] reference checks; [00:51:29] a month in the life of a COO; [00:52:52] energy levels; [00:54:53] leadership dynamics; [00:57:30] outsized career influences.
    Book a consult png image
  • From Zero to One in B2B Marketing: My Proven SaaS Playbook for Growth, Hiring, and Attribution

    From Zero to One in B2B Marketing: My Proven SaaS Playbook for Growth, Hiring, and Attribution

    Early-stage B2B marketing is where momentum is made or lost. In my product leadership work, I’ve seen that getting from zero to one requires uncommon focus, founder-led GTM discipline, and a tight feedback loop between product, sales, and marketing. In this narrative, I share the playbook I use—and the patterns I took from top operators—to help SaaS teams build credibility fast, compound learnings, and scale repeatable growth.

    Alex Kracov is the CEO and Co-Founder at Dock, and the former VP of Marketing at Lattice. Alex joined Lattice as the first marketer and third employee, and he helped to grow the business from seed to 1850+ customers. Prior to Lattice, Alex was a consultant at Blue State Digital — the team that elected President Obama and orchestrated projects at Google. Since leaving Lattice in 2021, Alex co-founded Dock, a B2B platform that has streamlined the customer buying experience for clients like Loom, Origin, and Instabug.

    Here’s the agenda I use to guide founders and early marketing leaders: the 2023 SaaS marketing playbook; how to start your early-stage B2B marketing; how to prioritize resources across multiple marketing bets; how to think about attribution; Lattice’s unorthodox million-dollar marketing campaign; how to hire for early marketing roles; what makes a standout marketer; and advice for building your first website.

    When I spin up early-stage B2B marketing, I start by defining the shortest path to signal. That means a crisp ICP, problem-first messaging, and one or two channels where our buyers already congregate. At this stage, I bias toward founder-led discovery calls, live product walkthroughs, and tight content that proves outcomes—not features. This creates the raw material for positioning, case studies, and a credible top-of-funnel narrative.

    Short-term versus long-term goals must be explicitly balanced. I set near-term pipeline and learning targets (e.g., qualified conversations per week, time-to-insight from experiments) alongside long-term brand assets (evergreen content, customer proof, category POV). The rule of thumb I apply: stabilize one growth motion before layering the next, so we don’t overfit to noise or dilute the message.

    Allocating resources across marketing bets is a portfolio problem. I structure it as 70/20/10: 70% on the core motion that’s already working, 20% on adjacent bets with clear hypotheses, and 10% on contrarian experiments that could unlock step-change distribution. Weekly syntheses convert experiment data into decisions—double down, redesign, or retire.

    On attribution, I’m pragmatic. Early on, precision is less valuable than directionality. I pair multi-touch analytics with qualitative inputs (self-reported attribution, sales notes, community signals). The question I ask: which narratives and channels consistently show up in won deals? That blend avoids over-crediting the last click and keeps us honest about how trust is actually formed in B2B.

    Your first website is a conversion engine and a trust anchor. The first thing people should see on your website is the problem you solve, the outcomes you deliver, and a frictionless way to see the product in action. I recommend a tight hero message, social proof above the fold, a short demo video or interactive experience, and clear CTAs for both buyers who are ready now and those who need to explore.

    Brand and positioning mature with evidence. I translate discovery insights into a simple hierarchy: category, problem, unique insight, product proof, outcomes. At Lattice, strong brand clarity met operational excellence; at Dock, product-led collaboration sells the value by making the buying experience itself the demo. In both cases, the lesson stands: great B2B brands tell a truth buyers can quickly verify.

    Bold bets can be force multipliers. Lattice’s unorthodox million-dollar marketing campaign underscores a principle I use sparingly but decisively: when the narrative, timing, and distribution are aligned, a high-conviction investment can set the agenda for your category. The bar is high. The insight must be non-obvious, the creative durable, and the measurement plan rigorous.

    Hiring for early marketing roles, I optimize for learning velocity, narrative craft, and cross-functional empathy. The ideal first marketer is a full-stack generalist who can research, write, ship, analyze, and partner with sales and product. Experience matters, but potential—ownership, curiosity, systems thinking—often outperforms. I scale the team once one motion is repeatable and there’s a clear backlog of work we can’t tackle without specialization.

    Conferences and communities are underrated if used deliberately. I set specific objectives (target accounts, partners, customer content) and treat events as field research and content engines. Every conversation informs messaging; every meeting has a next step; every session becomes a clip, post, or asset. The outcome is pipeline plus reusable proof.

    My 2023 SaaS marketing stack emphasizes speed to insight: product analytics to observe behavior; a CRM and marketing automation platform to orchestrate journeys; lightweight data pipelines for attribution; a CMS for shipping content fast; and collaboration tools that put buyers and sellers in the same workspace. What matters most is not the logo set—it’s the operating cadence that converts data into action.

    If you’re going from zero to one, keep it simple: validate your ICP, ship a compelling narrative, pick one channel to master, and measure what buyers say and do. Sequence beats scope. Credibility compounds. And the best marketing is a mirror of a product that solves a painful, urgent problem—beautifully.

    Timestamps: [00:00:00] Intro [00:02:45] The challenges and opportunities in early-stage B2B marketing [00:05:13] How to think about short-term versus long-term marketing goals [00:07:31] Allocating resources across marketing bets [00:09:13] Signs your marketing is working [00:11:20] The most underutilized marketing strategy [00:13:03] Creating your company’s first website [00:14:22] How Lattice formed its brand messaging and positioning [00:18:22] Dock’s innovative approach to marketing software [00:20:14] The first thing people should see on your website [00:23:10] Lattice’s most successful early-stage marketing tactics [00:28:05] Determining which marketing strategies are still relevant [00:30:25] Lattice’s unorthodox million-dollar marketing campaign [00:33:26] Why Alex had an outsized impact at Lattice [00:37:05] Lessons from his first marketing hires [00:39:41] When to scale your marketing team [00:40:55] Building an effective early-stage marketing team [00:42:30] A tough conversation with the CEO & Co-founder of Lattice [00:44:46] Achieving early-stage marketing alignment [00:46:20] Transitioning from employee to entrepreneur [00:49:19] Getting the most out of conferences [00:50:47] Selecting marketing channels in the early stages [00:52:44] Hiring marketers for experience versus potential [00:56:34] The 2023 SaaS marketing stack [00:58:19] Advice for Zero to One marketing [00:60:46] What successful B2B marketing looks like

    Referenced: Dock: https://www.dock.us/ Lattice: https://lattice.com/ Jack Altman: https://www.linkedin.com/in/jackealtman J Zac Stein: https://www.linkedin.com/in/jzacstein

    Where to find Alex Kracov: Twitter: https://twitter.com/kracov/ LinkedIn: https://www.linkedin.com/in/alexkracov Website: https://www.kracov.co/

    Where to find Brett Berson: Twitter: https://twitter.com/brettberson LinkedIn: https://www.linkedin.com/in/brett-berson-9986094/

    Book a consult png image
  • Supercharge Your Engineering Org: Alignment, AI, and Productivity from Adobe to Etsy

    Supercharge Your Engineering Org: Alignment, AI, and Productivity from Adobe to Etsy

    I obsess over building high-velocity engineering organizations that ship meaningful outcomes. When I evaluate what reliably moves the needle—across startups and scaled enterprises—it always comes back to alignment, disciplined management, and a modern view of engineering productivity. Recently, I revisited a set of insights that crystallize these themes and translate them into practical rituals any leader can adopt.

    Kellan Elliott-McCrea is a Head of Engineering at Adobe, overseeing Frame.io, a newly acquired video review and collaboration platform. He is known for his experience and expertise as an engineering leader. He was previously a VPE at Dropbox, and CTO at Etsy where he built and led a team of 300 people, from tech and platform reboot through to IPO. Kellan also built and scaled teams at Flickr, and has a coaching and advising practice for companies looking to supercharge their engineering teams.

    Here’s what we dig into when we talk about world-class engineering orgs: how software engineering has changed in the last 10-15 years; the future of software engineering, and the impact of AI; the importance of alignment and tactics for achieving it; how to think about and enable engineering productivity; lessons on culture from Adobe, Dropbox, and Flickr; concrete tips for being a better manager; and rituals for building business literacy throughout an org.

    Let’s start with a reality I see in my own work: engineering teams are bigger than they were a decade ago, despite dramatically better tools and platforms. The reason isn’t inefficiency—it’s scope. Today’s products carry higher bars for reliability, privacy, security, compliance, and multi-surface experience. The coordination surface area has exploded. That’s why operating models must evolve: clear interfaces between teams, standardized decision-making, and reliable cross-functional rhythms are no longer nice-to-haves—they’re throughput constraints.

    Alignment, then, is the ultimate speed multiplier. I’ve learned the hard way that slow teams are rarely under-skilled; they’re misaligned. “Slow teams are misaligned teams.” To counter this, I anchor on a few tactics: articulate a clear strategic narrative (why now, why us, why this), commit to outcomes vs output OKRs, and institutionalize decision logs so debates don’t reset every sprint. When teams know the customer problem, the business bet, and how their work ladders up, the flywheel starts turning.

    On engineering productivity, I avoid vanity metrics and favor a portfolio: flow and focus (interruptions, WIP), system signals (lead time, deployment frequency, change fail rate), and outcome alignment (how progress maps to customer value and revenue impact). Tools matter—DX investment in CI/CD, observability, and paved roads—yet the largest gains usually come from simplifying priorities and reducing cross-team coupling. Fewer, better bets will beat “more tickets shipped” every time.

    The future of software engineering is inseparable from AI. In my practice, I treat gen ai and gen ai for product prototyping as core accelerators: copilots for code and tests, scaffolding services that convert specs to boilerplate, and retrieval-augmented knowledge that collapses the gap between tribal lore and action. The key is to measure impact at the team level—cycle time, defect escape, and learning velocity—so AI augments engineering judgment rather than creating hidden complexity.

    Culture is the compounding edge. Lessons on culture from Adobe, Dropbox, and Flickr converge on a few essentials: invest in psychological safety and clarity of purpose, operationalize blameless learning, and make information radically accessible. “How Complex Systems Fail, by Richard I. Cook, MD” is a touchstone here—complexity punishes organizations that rely on heroics and rewards those that build resilient systems and shared mental models.

    For managers, I return to a short, durable list. Schedule real one-on-ones that prioritize coaching over status. Write more than you speak; clarity scales through documents. Run crisp, time-boxed decision forums with pre-reads and owners. Close the loop on feedback—especially in moments of disagreement—by documenting trade-offs and naming the decider. These concrete tips for being a better manager build trust, accelerate decisions, and enable autonomy.

    Every high-performing engineering org I’ve led invests in business literacy as a first-class ritual. I recommend monthly “Finance 101” briefings, customer support ride-alongs, and deal reviews to connect engineers to revenue realities. Pair that with tactics and rituals for enabling effective teams—weekly written updates, demo-driven reviews, and pre-mortems—and you get sharper prioritization and far better cross-functional coordination.

    Why so few companies successfully go multi-product? Most underinvest in platforms, shared services, and explicit funding models for internal APIs. The remedy: treat platforms as products with clear roadmaps, SLAs, and customer empathy; align incentives so teams don’t fork capabilities in the rush to ship; and adopt technical governance that favors standardization where it compounds and freedom where it differentiates.

    For compensation and career architecture, I pressure-test common models by asking: does this design reward the behaviors we say we want? If we value outcomes, impact, and enabling others, the ladders should reflect it. When the incentives match the mission, the org learns faster and scales cleaner.

    Referenced:

    Adobe: https://www.adobe.com

    Dropbox: https://www.dropbox.com/

    Flickr: https://www.flickr.com/

    Frame: https://www.frame.io/

    How Complex Systems Fail, by Richard I. Cook, MD: https://how.complexsystems.fail/

    How Etsy Grew their Number of Female Engineers by Almost 500% in One Year https://review.firstround.com/How-Etsy-Grew-their-Number-of-Female-Engineers-by-500-in-One-Year

    Where to find Kellan Elliott-McCrea:

    Twitter: https://www.twitter.com/kellan

    LinkedIn: https://www.linkedin.com/in/kellanem

    Website: https://kellanem.com/

    Personal blog: https://laughingmeme.org/

    My bottom line: if you want to supercharge your engineering org, anchor on alignment, measure what matters, and leverage AI to elevate—not replace—engineering judgment. Do that, and you’ll turn coordination costs into compounding advantages that show up in customer value, velocity, and morale.

    Book a consult png image
  • Building Products in a Post-LLM World: Hard-Won Lessons, Skeptic Busters, and Team Playbooks

    Building Products in a Post-LLM World: Hard-Won Lessons, Skeptic Busters, and Team Playbooks

    The ground rules for product development have changed in the post-LLM world. I’m sharing a practical, first-person playbook—lessons I’ve pressure-tested in my own product org—to help you build AI-native products with confidence, cut through hype, and deliver outcomes that compound.

    Sprig is an AI-powered user insights platform that has raised over $88m. Today’s discussion features two key individuals in Sprig’s journey so far: Ryan Glasgow, Sprig’s CEO and founder; and Kevin Mandich, Sprig’s Head of Machine Learning. Before Sprig, Ryan was an early PM at GraphScience, Vurb, and Weeby (all of which were acquired), and Kevin was an ML Engineer at Incubit, and a Post-Doctoral Researcher at UC San Diego.

    In today’s episode, we discuss: Key lessons from the Sprig founding story; Product development in the pre vs. post-LLM world; How to overcome AI skepticism; How to evaluate new models and how to know when to switch; Why you need an ML engineer; Sprig’s “AI Squad” team structure; How Sprig upskills all team members on AI.

    Founding story takeaways I keep returning to: conviction compounds when paired with continuous discovery. Early on, prioritize direct customer signal over elegant architectures. I’ve seen the fastest learning loops come from a tight PM–ML partnership that prototypes quickly, validates with real users, and refactors only after signal stabilizes. The Jobs to Be Done Framework: https://hbr.org/2016/09/know-your-customers-jobs-to-be-done remains my favorite lens to separate what the model can do from what the customer actually needs done.

    Pre vs. post-LLM product development requires a mindset shift. Pre-LLM, we wrote deterministic systems and pushed the edge with models like Google’s BERT model: https://en.wikipedia.org/wiki/BERT_(language_model). Post-LLM, we design probabilistic systems, treat prompts like code, and invest in evaluation harnesses from day one. I routinely prototype with Chat GPT: https://chat.openai.com and scaffold experiments with Langchain: https://www.langchain.com/ to compress discovery cycles. The key is shipping guardrails and UX affordances that make non-determinism feel trustworthy.

    On AI skepticism, I don’t argue—I demonstrate. I target one painful workflow, build a narrow, high-precision solution, and expose transparent failure modes with a human-in-the-loop escape hatch. This reframes AI from magic to leverage. In customer-facing settings (think customer support ai strategy), we measure deflection and satisfaction together so automation never outpaces user psychology.

    Evaluating new models—and knowing when to switch—demands a clear rubric: task quality (ground-truthed), latency at p95, unit economics, privacy/compliance, and operational reliability. I run shadow evaluations before swapping production dependencies, then phase changes behind flags with canaries and backstops. Tools like Auto-GPT: https://github.com/Significant-Gravitas/Auto-GPT are useful for ideation, but I never skip rigorous offline and online evaluation before a cutover.

    Why you need an ML engineer: the fastest teams pair a product manager who owns the problem framing with an ML engineer who owns the feasibility frontier. This duo translates ambiguous jobs into measurable tasks, instrumented datasets, and iterative model/UX improvements. In my experience, this partnership reduces time-to-learning more than any single tooling decision.

    Sprig’s “AI Squad” team structure mirrors what I’ve seen work: a cross-functional pod with a PM, ML engineer, data engineer/analyst, design, and platform partner. The squad ships thin slices end-to-end, owns their eval suite, and meets weekly to review errors, edge cases, and customer feedback. We track outcomes vs output OKRs to ensure velocity serves impact—not the other way around.

    Upskilling the entire team on AI is non-negotiable. I’ve had success with lightweight rituals: weekly demo hours, prompt libraries maintained in Jira: https://www.atlassian.com/software/jira, red-team exercises to uncover failure patterns, and internal brown bags where engineers and PMs teach each other. Small, frequent exposure beats heavyweight training.

    For deeper exploration and hands-on experimentation, I reference: Auto-GPT: https://github.com/Significant-Gravitas/Auto-GPT; Chat GPT: https://chat.openai.com; Google’s BERT model: https://en.wikipedia.org/wiki/BERT_(language_model); Jira: https://www.atlassian.com/software/jira; Jobs to Be Done Framework: https://hbr.org/2016/09/know-your-customers-jobs-to-be-done; Langchain: https://www.langchain.com/; Sprig: https://sprig.com/.

    Timestamps: (02:50) Intro (04:57) What attracted Kevin to Sprig (05:53) Kevin’s background before Sprig (07:56) How Ryan gained conviction about Kevin (09:55) Key technical challenges and how they solved them (18:46) How to overcome AI skepticism (21:47) The early difficulties of building an ML-enabled product (25:06) Evaluating new models and knowing when to switch (35:09) Using Chat GPT (37:23) Product development in the pre vs. post-LLM world (39:53) The impact of AI hype on Sprig’s product development (45:36) Balancing AI automation with user-psychology (48:47) Do recent LLMs reduce Sprig’s competitive advantage? (51:00) The importance of “selling the vision” to customers (54:40) How Sprig structures teams (57:25) How Sprig upskills all team members on AI (60:25) 3 key tips for companies trying to navigate AI (66:05) Major limitations with LLMs right now (70:27) The future of AI and the future of Sprig

    Three guiding principles I use daily: first, reduce surface area—start with one high-value job and earn trust with reliability. Second, treat evaluation as a product—version prompts, log failures, and continuously retrain on your own data distributions. Third, design for collaboration—pair AI with human judgment and transparent controls so users feel empowered, not replaced. Post-LLM success isn’t about chasing models; it’s about building resilient systems, teams, and learning loops.

    Book a consult png image