Part 8: Capstone Projects
Turning Knowledge Into Architecture
From Understanding to Practice
There's a version of a book on luck that ends at Chapter 40 and leaves you with a framework you find genuinely interesting, a set of concepts you can explain at a dinner party, and a vague intention to do something differently — starting soon, sometime after you've finished that other thing.
This is not that version.
The three capstone projects in Part 8 exist because knowing about luck science and actually using it are meaningfully different activities, and the gap between them doesn't close through more reading. It closes through doing — through designing an experiment, running it, observing what happens, and building the habit of treating your life as a system that can be iteratively improved.
The capstones are not assessments of whether you read the book carefully. They are invitations to find out what the book can actually do when it's in contact with your real life, your real network, and your real circumstances. The three projects span different scales — from deeply personal to organizational — and each one draws on a different cluster of the book's central ideas. You should choose the one that fits your situation, or attempt elements of more than one, or use the frameworks to design your own. The intellectual infrastructure belongs to you now.
The Three Projects
Capstone 1: The 30-Day Luck Experiment
The core idea: Design and run a controlled personal experiment in which you systematically implement one or more luck-increasing interventions from the book, track your results, and analyze what happened.
What this involves: The 30-Day Luck Experiment asks you to move from "I understand the theory" to "I can test the theory against my actual life." You will identify a specific domain — content creation, networking, professional opportunity-seeking, social connection, creative discovery — and design an intervention protocol grounded in the book's frameworks. You'll select the variables you're changing, define how you'll measure outcomes, run the experiment with genuine rigor, and write an analysis of your findings.
The Wiseman principles from Chapter 12, the luck journal method from Chapter 16, the opportunity surface expansion strategies from Chapter 25, and the curiosity practices from Chapter 26 are the natural building blocks. But the design is yours. The most useful experiments are the ones designed around a question the experimenter actually wants to answer.
What makes a good Capstone 1: - A clearly defined intervention (not just "be more open" but "attend three events outside my usual domain and initiate at least two conversations at each") - A measurable outcome variable (not just "more luck" but a specific proxy: new contacts made, opportunities identified, content engagement metrics, serendipitous connections documented) - A luck journal kept throughout, with honest daily or weekly entries - An analysis section that distinguishes between what the data shows and what you believe is causing it — including a serious engagement with alternative explanations and the small-sample problem from Chapter 7 - A reflection on what you would do differently in a second iteration
The best Capstone 1 projects don't just show that something worked. They show how you thought about designing it, running it honestly, and updating your beliefs based on what happened.
Capstone 2: Network Audit and Expansion Plan
The core idea: Systematically map your existing network, analyze its structural properties, identify the gaps that are costing you the most opportunity, and design a concrete plan to address them.
What this involves: This project applies the social network frameworks from Part 4 — weak ties (Chapter 19), small-world structure (Chapter 20), social capital and structural holes (Chapter 21) — to the actual network you have right now. You'll build a network map (visual or analytical), evaluate it across multiple dimensions, and produce a prioritized expansion plan grounded in the research rather than generic networking advice.
The network map itself asks: who are your strong ties and weak ties? In which domains? Are your connections clustered in one or two groups, or genuinely diverse? Where are the structural holes — the gaps between clusters that you could potentially bridge? Which domains that are important to your goals are underrepresented in your network? Who are the connectors and hubs you're adjacent to, and how well are those relationships maintained?
The expansion plan is specific and sequenced. Not "meet more people" but "identify three high-value weak ties in the field I'm trying to enter, using these specific channels, with these specific reactivation or outreach strategies, within this timeline."
What makes a good Capstone 2: - A genuine network map (not a curated version, but an honest one) - An analysis organized around the book's frameworks — structural holes, bridging vs. bonding capital, weak tie diversity — rather than impressionistic self-assessment - A prioritized list of specific network gaps, ranked by expected opportunity cost - A concrete, sequenced expansion plan with specific people, channels, timelines, and follow-up protocols - A section on the ethics of deliberate network building — drawing on Chapter 39 — that addresses how you plan to be genuinely valuable to the people you're trying to connect with, not just extract value from
The Capstone 2 projects that work best treat this not as a one-time exercise but as the foundation of an ongoing network management practice. The final section should describe how you'll maintain and evolve the system beyond the initial project.
Capstone 3: Build a Serendipity Engine for a Real Organization or Community
The core idea: Apply the serendipity engineering principles from Part 5 to design a luck-increasing system for a team, club, community, or organization you're actually part of — and if possible, pilot it.
What this involves: Most luck science is applied individually. This project applies it organizationally: if individuals can engineer more serendipity through deliberate behavioral and environmental design, what does that look like at scale? How do you design a team meeting structure, a club's events calendar, an online community's interaction architecture, or a classroom's physical and social arrangement to maximize the rate of valuable unexpected connections?
The theoretical foundations are in Part 5 (serendipity engineering frameworks, opportunity surface, prepared mind), Part 4 (network structure, structural holes, weak ties within organizations), and the signal-to-noise problem from Chapter 32. The application is organizational design.
You'll analyze an existing organization's current luck architecture — what serendipitous encounters does the current structure enable or prevent? — and then design specific interventions: a new event format, a modified communication structure, a cross-departmental project structure, a physical space redesign, a community ritual. If you can pilot even a single intervention and document the results, the project becomes substantially richer.
What makes a good Capstone 3: - A genuine diagnosis of the organization's current serendipity deficit — specific, not generic - At least two intervention proposals grounded in the book's frameworks, with explicit reasoning about why these interventions should work - An implementation plan that addresses the human and logistical realities of actually changing an organization's patterns (not just the ideal version) - A measurement plan: how would you know, six months later, whether the serendipity engine was working? - A reflection on what the project taught you about the difference between individual and organizational luck engineering
The best Capstone 3 projects engage with the structural luck questions from Part 4 and Part 7 — specifically, they ask who in the organization currently has the most access to serendipitous encounters, and whether the proposed design improves that distribution or merely optimizes for those who are already advantaged.
How to Choose
Choose Capstone 1 if you want to understand your own luck patterns more deeply, if you're at a point in your life where a personal behavioral experiment is most actionable, or if you're a creator or content professional and the 30-day framing maps naturally onto your workflow.
Choose Capstone 2 if you're navigating a significant career or professional transition, if the network analysis chapters (Part 4) produced the most recognition and urgency for you, or if you have a concrete goal — a job, a collaboration, an introduction — that network redesign would directly serve.
Choose Capstone 3 if you have a leadership role, formal or informal, in an organization you want to make luckier, or if the organizational and systemic scale of the problem is where your energy and interest are. This project requires access to an actual organization, so it won't suit everyone — but when it fits, it's the most socially impactful of the three.
There is no wrong choice. There is only the choice that is actually yours, suited to your actual circumstances.
What Makes a Good Capstone
Across all three projects, the following properties distinguish work that genuinely develops the author's relationship to luck science from work that performs familiarity with it.
Honesty. The most valuable capstone projects are the ones that report what actually happened, including the parts that didn't work. A 30-Day Luck Experiment that failed to produce measurable outcomes but generated clear insight into why is more intellectually valuable than a success story that glosses over contrary evidence. The small-sample problem from Chapter 7 applies here too: you cannot draw grand conclusions from one month of personal data. What you can do is reason carefully about what the data suggests and what you'd need to see to have more confidence.
Specificity. "I worked on my network" is not a capstone. "I identified three structural holes in my network, reached out to eight people across two weeks using the reactivation scripts I designed, had meaningful conversations with five of them, and mapped the resulting changes to my network diagram" is a capstone. The specificity is not a formality — it's what makes the exercise actually teach you something.
Framework fidelity. A capstone that uses the book's frameworks as genuine analytical tools — not just name-dropping terminology but actually applying the logic — will produce better insight than one that uses the language decoratively. When you write "structural hole," you should be able to point to the specific gap in your network map that the term refers to.
Ethical awareness. Chapter 39 asked you to think about what it means to use luck ethically — to be the kind of person who generates luck for others, not just extracts it from them. Good capstone work carries that awareness into the methodology. A network expansion plan should include a section on how you'll be genuinely useful to the people you're connecting with. A serendipity engine for an organization should ask who it serves and whether it serves them equitably.
A personal stake. The best capstone projects are the ones designed to matter. If you're indifferent to the outcome, the work will reflect that. The question that drives the experiment, the network gap that the audit is designed to address, the organization whose luck you want to improve — these should be things you actually care about. Luck science is not a classroom exercise. It is an applied discipline, and applied disciplines work best when they're applied to something real.
What Comes After
Students and readers who have completed serious capstone work with this material have gone on to do things worth mentioning — not because they are remarkable people (though they are) but because they show what luck science in practice looks like.
A recent graduate who ran a 30-Day Luck Experiment focused on informational interviews rebuilt her entire job search strategy around the weak-ties finding from Chapter 19. She started reaching out to people two and three degrees removed from her current network rather than people she already knew. Within six weeks, she had an offer through a connection she'd never heard of when the experiment began.
An undergraduate who designed a serendipity engine for his university's entrepreneurship club introduced a monthly "random pairing" event — structured one-on-ones between members from different majors, randomly assigned. Within a semester, two collaborations that had arisen from those pairings had launched as actual student ventures.
A content creator who kept a luck journal for sixty days discovered that her three most successful pieces all originated from the same kind of situation: something she'd been curious about for months but had assumed was "too niche." She redesigned her content strategy around that finding. Her channel's growth rate doubled.
None of these are magic. All of them are applications of ideas you now have the tools to understand, reproduce, and adapt. The experiments will not all work. The network audits will reveal uncomfortable truths. The serendipity engines will be harder to build than the theory suggests. This is exactly as it should be. Luck science is not a vending machine. It is a discipline — and disciplines develop through practice, failure, iteration, and the stubborn conviction that understanding something clearly enough is worth the time it takes.
Dr. Yuki Tanaka ended the semester with a question. Nadia, Marcus, and Priya each left with a different answer — and with the sense that the answer would change over the years, as they changed, as the circumstances they found themselves in changed, as the luck they built compounded and the luck they didn't build failed to arrive.
That's the right relationship to have with a field of study. Not certainty, but orientation. Not a fixed answer, but a better question.
You have the frameworks now. Go build something with them.