TechCrunch put 'tough decisions, and constant reinvention' on a conference agenda. The question that asks whether you have made one.
On September 22, 2026, TechCrunch published the agenda for its own Founder Summit, a one-day event at Boston's SoWa Power Station on November 4. The piece is promotional and says so, closing with a note that TechCrunch may earn a commission when readers buy through its links. The agenda is still worth reading as a document about how experienced operators describe hard decisions. The pitch is that attendees get "direct access to the investors and founders" who have already made the calls now in front of them. Brian Halligan, the HubSpot co-founder and Sequoia partner, is billed to speak on building companies through "rapid growth, tough decisions, and constant reinvention." Vineet Edupuganti, co-founder and CEO of Cogent Security, will according to TechCrunch cover how founders "navigate trade-offs, and think beyond valuation" after Cogent Security raised an $11 million round. Kent Bennett of Bessemer Venture Partners is scheduled to unpack "the decisions that separate enduring companies from expensive experiments."
Read the agenda for the behavior it keeps circling rather than the topics it lists. Each of those sessions is about a leader changing course while people with money and opinions are watching, and often objecting. Reinvention is never a solo act. When a company pivots, someone on the cap table backed the old plan, someone on the team was hired to execute it, and someone in sales has already promised it to a customer. The summit sells the idea that borrowed judgment can soften that ordeal. An interviewer wants the opposite. They want evidence that the candidate has already lived through one such call without a panel to defer to, and can account for it plainly, including the part where the objectors had a point. That is why a phrase from a conference agenda is also, exactly, an interview question.
Why they ask it
The question compresses three assessments into one story. The first is judgment: was the change actually warranted, or was it restlessness dressed up as strategy? The second is influence: how did the candidate move people who had a legitimate stake in the original direction? The third is integrity: did they listen to the disagreement, or route around it? A manager who has never pivoted against opposition has either never owned a strategy or has only changed course when it was safe to do so. Neither is what a senior role needs. Hiring panels ask this because the next reorganization, budget cut, or product bet will put the candidate in exactly this position, and they want to know what happens when consensus is not available.
The trap
There are two common failure modes, and they are mirror images. The first is the consensus story. The candidate describes a pivot in which everyone eventually agreed, the disagreement lasted one meeting, and the story ends with alignment. The interviewer hears no risk, no cost, and no evidence that the candidate can act before agreement arrives. The second is the hero story. The candidate was right, the stakeholders were wrong, the pivot worked, and vindication arrived on schedule. That reads as someone who does not update their view, and it leaves the interviewer wondering how the candidate behaves when the stakeholders turn out to be right. A third, quieter trap is skipping the original strategy entirely. If the answer never explains why the old direction made sense at the time, the pivot sounds like drift rather than a decision.
Applying STAR-T
Situation. Set the original strategy and give it a fair hearing. "Our platform team was months into consolidating several internal event pipelines into one. The plan had executive sponsorship, a budget line, and a launch date that finance had already used in its forecast." The listener should understand why reasonable people were committed to the plan before it changed.
Task. Name the moment the evidence turned, and be specific about what the candidate owned. "Partway through, production incident data showed that the reliability problems we were solving for came from a single legacy pipeline, not from having several. I owned the recommendation on whether to finish the consolidation or narrow the work."
Action. This is where the disagreement lives, and it deserves real weight. Name who objected and what their reasoning was, in terms they would accept. "The product lead disagreed because the consolidation was a visible commitment to customers. Finance disagreed because the forecast assumed the retired pipelines would cut infrastructure cost. I wrote up both objections before my own case, brought the incident data to a joint review, and proposed narrowing scope to the legacy pipeline with a checkpoint to revisit consolidation later." The strong version shows the candidate arguing their case while protecting the objectors' interests inside the new plan.
Result. Report what happened, including what did not happen. "We shipped the narrow fix within the quarter and incident volume dropped. The full consolidation was not revived, and the cost savings finance had forecast did not materialize that year."
Trade-off. This question rewards a stated cost more than most. "The product lead was right that we lost some credibility with customers who had been told a unified pipeline was coming. I would make the same call again, but I would have looped in the account team before the joint review rather than after it." That last sentence separates a confident answer from a defensive one.
The follow-up that breaks weak answers
The follow-up an experienced interviewer reaches for is some version of: "What were the people who disagreed right about?" The consensus story cannot answer it, because there was no real disagreement to be right about. The hero story cannot answer it either, because conceding the objectors had a point undercuts the vindication. A strong answer has already done the work. It names the specific thing the objectors saw that the candidate underweighted, says whether the pivot still holds given that cost, and describes what would change next time. The summit agenda promises founders they can learn from people who already made the hard calls. The interviewer is checking whether the candidate is one of those people, and the surest tell is whether they can describe the argument they lost inside the decision they won.
Score your answer against the director’s bar
Q: Tell me about a time when you pivoted strategies and stakeholders disagreed.
Bank the pivot where someone credible disagreed with you, and rehearse it until the cost is as clear as the win. Try it free →