采取这个具体步骤：你的计划应该与人们实际所做的事情联系起来，并通过快速实验来调整。Dennis Crowley 于 2009 年与 Naveen Selvadurai 共同创立了 Foursquare，旨在将简单的签到转化为本地发现的实用信号。早期的产品提供提示和徽章，最初的几个月里有一千多家场所加入。他们证明了真正的价值来自用户如何看待它们——他们想去的地方——而不是仅仅来自炒作。他们想要构建商家与附近客户联系的工具。
这条路径表明了坚韧如何在日常工作中体现出来。Crowley 建立了一种文化，在这种文化中，数据解释了每个决策背后的原因，而不是猜测。即使数据看起来很紧张，他仍然让团队一次专注于一个问题，并以冷静的态度回应用户的反馈。当该产品拆分为两个应用程序时，出现了显著的变化，Swarm 用于签到，Foursquare 用于城市指南，这一举措扩大了受众，而又没有失去核心意义。
许多团队都在追逐迅速成名； Crowley 将日常工作与多年来建立的长期实践联系起来。他让团队专注于朝着可靠产品前进的难题。就我个人而言，他说核心信号来自与实际使用该服务的人交谈。他不会满足于虚荣指标，并保持紧密的反馈循环。
构建这个平台并非易事；团队必须围绕共同的节奏和严格的测试保持一致。值得注意的里程碑包括拆分为 Swarm 和 Foursquare，这一举措在保持数据质量和稳定增长的同时，提高了对签到和发现的关注度。
在扩展之前，应用以下步骤：将单个用户任务与狭窄的测试联系起来，收集数据，并解释发生了什么变化。经常与客户会面，分享一份清晰、具体的简报，并且只有当证据表明这样做时才进行调整。通过许多小实验，你可以将最初的动力转化为持久的进步，并在你周围建立韧性。
简而言之，坚韧意味着与用户保持紧密联系，保持紧密的反馈循环，并将原则转化为实践。Crowley 的道路表明，如果保持冷静的节奏并从每一个错误中学习，一个小团队可以在多年内影响许多人。难道你不想将这些想法应用到你的下一个项目中吗？
从 Dennis Crowley 到加利福尼亚和斯坦福 GSB：坚韧的实用课程
首先制定一个具体的 90 天 MVP 计划，你可以在本地进行测试，然后计划搬到加利福尼亚，以利用充满活力的创业集群。如果你是一名对自己的想法充满信心的学生，梦想着产生影响，记录下每一个证实或挑战它的时刻；在你的办公桌附近记笔记，并用它们来磨练你向投资者的推介。由于每一次挫折都会增强决心，因此将工作视为你每天都在改进的工艺，而不是单次推动。
文化塑造坚韧。谦逊让你脚踏实地；你将其带入每一个想法和对话中。当你听到评论或笔记时，你会给予关注并应用它。你追求的明星不是一枚徽章，而是你从同伴和导师那里学到的稳步进步。这个世界奖励清晰的倾听和切实的行动，而不是虚张声势。
保持种子心态：进行小额投资，快速测试，并迭代。喜欢与要求明确性的投资者进行对话。每一次转变都成为进步的证明；你为产品贴上的第一个标签奠定了基调，并在艰难的场合保持昂首挺胸。当进入新市场时，倾听行业内的声音并调整你的方法。
从丹尼斯·克劳利的加州一步到斯坦福GSB的参与，实际的教训是将每一次遭遇都视为毅力的考验：早到，做笔记，并将学习转化为执行。在加州，你绘制一条将用户需求与持续努力联系起来的路径。在斯坦福GSB，你将这种纪律转化为同行评论和清晰的决策。
要将这些经验应用到今天，制定一个简单的12周计划：1) 确定你的90天测试，2) 在加州找到导师，3) 制定一套清晰的里程碑以证明发展势头，4) 记录结果，以便你可以与投资者分享一个引人入胜的故事。相信这个过程，不断前进，并知道我们通过你投入的每一刻都建立了势头。
确定一个精确的用户需求，并通过一个简单的、可追踪的指标来验证它
说出一个由你最初的市场对话所命名的单一的、真实的用户需求，并通过一个你可以在一周内追踪的简单指标来验证它。选择一个证明价值的核心行动，并围绕它设计一个最小化的实验。如果你发现了早期的信号，你可以更快地行动；尽管这条道路可能感觉艰难，但这种专注能让团队保持前进。
证明这一需求并且可以在七天内追踪到的最小行动是什么？将其定义为激活：新用户在一周内执行核心行动的比例是多少？标记每个队列，向董事会讲述这个故事，并坦率地谈论这些数字的含义，即使它们是早期的且不完善的。
建立一个种子原型，以最小的特性来满足需求。使用简单的工具并追踪一个单独的指标：七天内的激活。与来自市场的50-100名用户一起运行测试，保持范围小，以便你可以快速学习。保持标签简单，并将行动与产品相关联，以便你可以向利益相关者讲述一个关于潜在规模的有趣故事。
将结果视为前进道路的明确信号：如果激活率徘徊在20-25%左右，并且第一周的留存率稳定，则市场可能支持一个有利可图的产品，你可以朝着规模化发展。如果该指标保持在10%以下，则肯定要重新考虑需求或进行调整。这种方法有助于企业决定资助什么和放弃什么。此外，寻找数据中表明势头良好的上升趋势。
丹尼斯·克劳利表现出了将一颗微小的种子变成董事会可以信任的东西的毅力。他与用户交谈，讲述数据故事，并将威尔逊带入对话中，以对齐后续步骤。他通过改进标签和用户流程，将早期信号转化为实际产品，将这个想法推销给团队，并像许多创始人一样，不断前进。
要自己应用这一点，请选择一个已知的需求，运行一个为期一周的种子测试，并告诉自己保持简单和容易。追踪该指标，告诉那些向你推销这个想法的人，并用标签和清晰的规模化路径与董事会交谈。这个过程帮助我，我自己和团队专注于实际推动市场并将想法转化为产品的东西。这与进行更大的投资无关，而是与学习有关。
交付一个精益MVP，以收集真实的用户反馈并快速迭代
交付一个精益MVP，其中包含一个核心功能，可在10天内交付价值，以收集真实的用户反馈并快速迭代。
当您专注于一个问题时，这将变得更容易。梦想一个完整的产品不是必要的；你必须交付一个小型的原型并快速学习。保持范围紧凑，并在扩展之前验证风险最高的假设。
Define a narrow audience and cant trust a broad sample. Both early adopters and power users can contribute, but you should test with one clear group first. A compact plan helps you move faster and learn without getting stuck in thinking about every edge case.
Build a minimal version that actually worked in practice for other teams. Avoid bloating the flow; include only what proves value and what you can measure. If something didn’t perform, iterate on the core interaction rather than overhauling the entire UI.
Instrument minimally: in-app prompts, a short three-question survey, and optional 15-minute interviews. Capture a comment and, when users tell you which part mattered most, theyd told us that the simplest path often holds the answer. They may share tough trade-offs, but you can learn from them and adjust quickly. Theyll see that you listen, which fuels future engagement.
News from early users helps you decide next steps and keeps the team aligned. Over years of developing products, teams played with dozens of approaches; this lean path grows the chance of a successful outcome while avoiding wasted effort. The aim is to learn fast, then ship the next single improvement that moves metrics in a meaningful direction.
| Action | Rationale | Metric | Timeline |
|---|---|---|---|
| Define single hypothesis and target user | Focuses effort and reduces risk | sign-ups from target group; activation rate | before MVP release |
| Build minimal prototype for core flow | Validate core value with minimal overhead | time to first usable session | 10 days |
| Collect feedback via prompts and interviews | Captures both numbers and stories | comments count; interview sessions | 2 weeks |
| Decide iteration and next change | Base on signal, not guess | retention or activation improvement | end of sprint |
Frame setbacks as experiments with timeboxed iterations and guardrails
Start by treating every setback as a testable hypothesis and lock a timebox of 5–14 days to learn something concrete. This creates momentum, reduces debates, and lets youre move forward with data instead of opinions. In crowleys moments, setbacks signal what to test next and you identify the next experiment quickly, like a musician fine‑tuning a track until the rhythm feels right.
Frame the setback as a precise hypothesis. Write one sentence: If we change X for users in Y condition, then Z outcome will occur. This keeps the team focused and makes it solvable within the timebox.
Timebox with guardrails. Set a period of 5, 7, or 14 days depending on complexity, and declare a preplanned stop date. If you reach the guardrail thresholds, you pause or pivot; if not, you proceed to the next step.
Define guardrails clearly. Budget cap, risk threshold for negative user impact, and a decision gate (continue, pivot, or kill) because those boundaries keep the effort accountable and reduce the gamble.
Choose concrete metrics. Use a leading indicator (activation or engagement within the first 3–7 days) and a trailing indicator (retention after 14 days). Mark the experiment as solved when the hypothesis meets its criteria or is decisively disproven.
Regular, short talks and updates. Schedule quick talks every periods to share findings, and send a concise email with the learnings. This creates a single source of truth and keeps the union of teams aligned.
Document and create a reusable learnings memo. Capture what worked, what didn’t, and why. A simple template helps teams reuse insights across launches and protect culture from silos.
Maintain humility and openness. Talk openly about failures, acknowledge what you solved, and invite input from diverse voices because that culture grows stronger when people feel safe to voice concerns.
Decide next steps and advance. If the hypothesis is validated, launch the next iteration; if not, adjust the X variable and run another timeboxed test–again and again–until you identify a viable option to move forward.
Example scenario: you want to raise onboarding activation from 14% to 22%. Frame the hypothesis, timebox 10 days, set guardrails (max spend $2k, no negative NPS impact beyond -5), track activation and 7‑day retention, and document the outcome in an email to the team. If activation hits 21% within the period, you proceed to launch; if not, you test alternative copy or a shorter onboarding flow. This approach mirrors how crowleys teams identified the next test after each launch, turning setbacks into a steady stream of experiments that fuel forward momentum, not fear, and keep the culture grounded in humility and evidence.
With this method, music and momentum align; you take down barriers to learning, reduce risk, and create a repeatable pattern that every period helps businesses grow. The option to advance remains clear, because each learning cycle delivers data that informs the next decision, and the organization moves forward with intention, not hesitation.
Tap the Bay Area ecosystem and Stanford GSB networks for mentorship and resources
Reach out to crowleys-aligned mentors in the Bay Area and Stanford GSB alumni who run weekly mentoring circles; this union delivers quick feedback, access to executives, and concrete resources that does accelerate a startup's next moves, with thrilling, practical insights.
Next, map out who to talk to: executives with track records in scaling, product leads who critique prototypes, and founders who have navigated tough funding cycles while building. Look for places where these groups converge, then sent your intro notes with a tight one-pager to unlock bigger opportunities than before, through coaching andor advisory tracks.
Talking with dozens of mentors, theyd said that different programs fit your startup's culture and growth stage across periods; the next turns often include 15-minute chats, then longer sessions, and mentors wanted to see real progress, which can unlock millions in value.
Finally, implement a weekly rhythm: sent intros to 5-7 mentors, track responses, and schedule 3-4 pilot conversations. If you went through a Bay Area network, you would see faster feedback and bigger chances for collaboration. Another useful habit is documenting what works and what doesn't, which compounds over time.
Build repeatable processes and a team culture that sustains grit through growth
Define a razor plan and lock it into a weekly cadence: decisions logged, owners named, outcomes dated, and risks pushed down to the owners for action. This razor clarity feeds speed and reduces confusion when markets shift, so youve got a stable baseline to push from, and you can stay sure about the path.
Pair the plan with a living playbook: a 2-page decision log, a simple post-mortem template, and a quarterly health check on team confidence. Capture what changed, why it happened, and what helped the team adapt next. Include a steady haul of metrics so the team can see not only output but the effect on customers; avoid duplicative steps; each item has a single owner and a ready-to-share note. We wrote a short memo to capture the rationale behind the changes.
建立一种鼓励来自各个角落的声音的文化：工程师、设计师、艺术家、营销人员和公众客户。一个专门的学习板块浮现洞察和反复出现的经验，同时每个贡献都会得到对其贡献者的明确反馈。这减少了孤岛效应，并支持不断壮大的团队保持一致，而无需增加额外的会议。寻找行为和结果中的信号，以验证每个声音都塑造了决策。我提醒自己，反馈是燃料。工作节奏在简单的仪表板中保持可见。
通过简洁的笔记和简单的仪表板，让投资者和公众了解最新情况。我们编写了投资者可以扫描并寻找下一步行动信号的简洁笔记；在 Twitter 上和团队中分享进展，突出一个令人兴奋的、值得注意的胜利以及每个转折点背后的原因。当信号公开发送时，信任就会增长；当信号保持在内部时，团队行动会更快。
扩展文化的下一步：授权管理者保持节奏，培训新领导者学习流程，并编纂异常路径。记录决策如何在人员流动中幸存下来，以及新员工如何加速勇气。你必须衡量参与度并调整方法；评论反馈并将其分配给负责人。在这个世界里，可预测的例行程序胜过混乱。
