Week 4, Operationalize · Day 27 of 30
Day 27: 30-day retrospective, what the framework caught
Four weeks. Three candidates. One calibration. Ten watchlist orgs. What's measurable?
Day 27 in one paragraph: By Day 27 you have ~30 datapoints across ~13 orgs (3 candidates + 1 calibration + 10 watchlist + retroactive portfolio). That's enough to write a one-page retrospective that proves to yourself the framework is or isn't worth keeping in your process. You will spend about five minutes, end with a concrete artifact, and the whole curriculum stays free at this URL permanently.
Where this day sits in the 30
Week 4 wires the system into alerts, sharing, and agent integrations so it runs without you. Day 27 of 30 sits 90% of the way through, in week 4, operationalize, one of four one-week phases. This day also carries a bonus exercise for anyone with extra time. Everything in this challenge is built from public GitHub signals, the same data that powers the weekly deal-flow feed, and the day's lesson is worth roughly €79 in equivalent consulting time by the anchoring we use across the curriculum.
Yesterday
Yesterday you customised the weights. Today: the audit. Did the framework earn its slot?
Why this signal matters
By Day 27 you have ~30 datapoints across ~13 orgs (3 candidates + 1 calibration + 10 watchlist + retroactive portfolio). That's enough to write a one-page retrospective that proves to yourself the framework is or isn't worth keeping in your process.
The 5-minute exercise
- 1List every score you ran in the last 30 days. Org + composite + delta-vs-gut.
- 2Count: composite >gut (framework added value) vs composite =gut (framework confirmed) vs composite <gut (framework saved you).
- 3Identify any specific deal flow you wouldn't have surfaced without the framework.
- 4Write the one-paragraph retrospective: what's keepable, what to drop.
What you’re filtering for
A retrospective that you'd be willing to share with a peer investor. If you can't articulate one specific case where the framework changed your decision, that's also a valid result, note it and decide accordingly.
Edge case
Sometimes 30 days isn't enough to see attribution because rounds take 60-90 days to close. In that case, schedule a 60-day follow-up retrospective to revisit the watchlist and check actual outcomes.
Bonus
The retrospective doc becomes the foundation of the next 30 days. The framework either earns a permanent slot in your process or it doesn't, and now you have the data to defend the choice.
Tomorrow
Tomorrow: the Sunday digest as continuous practice, turning the 30-day muscle into a forever rhythm.
Common questions about day 27
- How long does day 27 take?
- About five minutes of hands-on work against the org you picked on day one. The reading adds another two or three. If you are short on time the exercise alone still delivers the day's point.
- Do I need any tools or paid data for 30-day retrospective, what the framework caught?
- No. Every exercise in the challenge runs on public GitHub data and a browser. The feed that automates the same checks is available, but the curriculum itself is deliberately tool-free so the habit lands before the tooling.
- What if I miss a day?
- Every day is permanent at its own URL, so you can pick up exactly where you stopped. The sequence matters, each day builds on the previous one's artifact, but the pace is yours. Many people run the 30 days across six or seven weeks instead of four.
Curriculum: /challenge · Methodology: /methodology · Paper: ssrn.com/abstract=6606558