Daniel sent us this one about something that's been quietly shaping policy for decades — the summer school model. Not the kind where you learn algebra, but a residential, week-long gathering of parliamentarians, academics, and practitioners who lock themselves in a villa or a retreat center and try to actually solve a specific problem. He's asking how these got their start, what the famous examples are, and — this is the part I think is most useful — how a facilitator would actually go about organizing one. Scope, participant selection, whether these can be annual things. There's a real playbook here, and most people who try to run these get it wrong.
They get it wrong in predictable ways. The RAND Corporation did a study in twenty twenty-three that found policy summer schools have a three-point-two times higher idea-to-implementation rate compared to traditional conferences. That's not a marginal improvement. That's a completely different category of outcome.
Three-point-two times. So the standard conference — with its lanyards and its parallel tracks and its panelists reading slides at you — is basically a rounding error in terms of actually changing anything.
Yet we keep doing them. The conference industrial complex just churns along. But the summer school model has been producing concrete policy for sixty years, and most people in the policy world have never heard the term. They might have experienced something like it, but they don't know there's a design discipline behind it.
Let's start with what it actually is, because the name is terrible. When I first heard "policy summer school," I pictured remedial classes for underperforming ministers.
The name is historically entrenched and completely misleading. A policy summer school is a time-bound residential gathering — typically five to ten days — of twenty to forty people from different sectors, focused on a single policy challenge. No formal presentations. Heavy emphasis on facilitated small-group work. The output is a shared problem frame and usually a draft white paper, a pilot design, or a legislative blueprint. The "school" part isn't about being taught — it's about being schooled by the problem and by each other. It's a co-creation workshop, not a teaching event.
It's a retreat where the problem is the teacher and everyone shows up as a student. That's the metaphor.
It's distinct from an academic summer school, which teaches existing knowledge to students. And it's distinct from a conference, which is about broadcasting findings to an audience. The policy summer school flips the dynamic — participants arrive with expertise but are expected to leave with something they didn't have before. The distinction that matters is: are you disseminating, or are you co-creating?
The "summer" part? Is that just because academics have summers off, or is there something deeper?
It's partly historical — the first ones were literally held in the summer, because the original participants were mostly academics and parliamentarians whose schedules freed up in July and August. But there's also a seasonal argument: summer implies a certain psychological openness. People are more willing to be intellectually playful when the weather's warm and they're not in their usual institutional settings. The Salzburg Global Seminar, running since nineteen forty-seven, holds sessions year-round, but the summer ones have always had a particular energy. I don't think seasonality is essential, but the association has stuck.
Alright, so we've got the definition. A residential co-creation workshop with no audience and a hard output. Now — where did this actually come from?
It really crystallized in the nineteen sixties, and there are a few origin points that all converged. The first is the Ditchley Foundation in the UK, founded in nineteen fifty-eight. Ditchley Park is this enormous eighteenth-century country house in Oxfordshire, and from the start, the model was residential, small-group, off-the-record discussions on policy challenges. They've hosted over twelve hundred of these since nineteen fifty-eight, averaging thirty-five participants per event.
Twelve hundred gatherings. That's basically a policy factory disguised as a stately home.
The format hasn't changed much. No audience, no press, strict non-attribution rules. But Ditchley was Anglo-American focused. The model that really expanded the format to domestic social policy came a few years later, in nineteen sixty-four, at the University of Sussex.
This is the one I want to hear about. The Sussex summer school.
Richard Titmuss and Brian Abel-Smith organized the Summer School on Social Policy at Sussex in nineteen sixty-four. Titmuss is arguably the most influential social policy thinker Britain ever produced — he essentially invented the academic discipline of social administration. Abel-Smith was his collaborator and a key advisor to the Labour Party. They brought together thirty-two people — Labour MPs, civil servants, academics, and a few practitioners from the voluntary sector — and spent a week designing what became the UK's Supplementary Benefits system.
Which is not a small program. What was the scale?
At its peak, Supplementary Benefits served four and a half million people. It was the safety net for everyone who fell through the cracks of the National Insurance system. And it was designed, in large part, in a week-long residential workshop in Sussex. That's the origin story that matters — not a parliamentary committee, not a royal commission, not a think tank report. A small group in a room, with a clear problem, a deadline, and no audience to perform for.
Titmuss and Abel-Smith essentially invented the format for domestic policy. But there's a parallel track happening around the same time — the Bellagio Center.
The Rockefeller Foundation's Bellagio Center on Lake Como in Italy. The foundation acquired the villa in nineteen fifty-nine, and by the mid-sixties it was hosting what became known as the Bellagio Conferences. The format was deliberately residential and deliberately luxurious — not for comfort's sake, but because isolation plus beauty creates a particular kind of intensity. You can't easily leave. You're surrounded by water and mountains. You're forced to sit with the problem and with each other.
The Lake Como effect. You're too far from an airport to storm out.
The Bellagio model introduced something that became standard practice: the "Bellagio Rules." Similar to Chatham House Rule, but with a twist — no attribution, no recording of any kind, but participants are explicitly permitted to use the ideas freely in their own work. So you can take the insight and run with it, but you can't quote anyone. It creates a safe space for intellectual risk-taking.
That distinction between attribution and usability is subtle but important. Under Chatham House, you can use the information but not identify the speaker. Under Bellagio, you can use the ideas as if they were your own — the provenance is erased entirely. That's a stronger commitment to idea mobility.
It changes the incentives. If you know your brilliant suggestion won't be credited to you, you're more likely to share it, because there's no reputational risk if it turns out to be half-baked. But you're also more likely to share it because there's no reputational reward — you're contributing to the collective output, not building your personal brand. That's the opposite of a conference, where the whole point is to be seen saying something smart.
You've got Ditchley, Sussex, Bellagio — three different lineages all converging on the same format. What was it about the nineteen sixties that made this take off?
A few things converged. First, the post-war expansion of the welfare state meant there were suddenly enormous new policy systems that needed design work — and the traditional civil service machinery wasn't equipped for it. Second, the social sciences were professionalizing rapidly, and there was a new appetite for evidence-informed policy. Third, air travel had become accessible enough that you could gather thirty people from different countries for a week without it being a logistical nightmare. And fourth — and I think this is underappreciated — the nineteen sixties had a particular cultural openness to experimental formats.
The workshop as counterculture. So let's talk about some of the famous examples beyond the origin stories.
The one I find most instructive is the Bellagio Initiative on Global Health, which ran from two thousand five to two thousand seven. Three sessions, a hundred and twenty participants total, convened by the Rockefeller Foundation. The specific challenge was: how do we design a global financing mechanism for the three big infectious diseases? The output directly influenced the design of the Global Fund to Fight AIDS, Tuberculosis and Malaria.
The Global Fund has disbursed what — sixty billion dollars at this point?
Over sixty billion as of twenty twenty-five. It's one of the most consequential global health institutions ever created. And the design choice that made the Bellagio sessions work was something very specific: they banned PowerPoint.
Of course they did.
Every participant had to submit a two-page provocation paper in advance. That's it. You had to distill your thinking into something that could be read in ten minutes. And then the sessions were structured around those provocations, not around slide decks. The facilitator would say: "You all read Maria's paper. Maria, what's the one thing you most want the group to wrestle with?" And then they'd go.
The two-page provocation paper is such a good forcing function. It says: you have something to contribute, but you don't get to dominate the room. It also means everyone arrives having done the reading. There's no faking it.
The ban on PowerPoint eliminates the single biggest pathology of policy gatherings — the presenter who brought forty slides and is going to get through all of them regardless of what the room needs. Once you remove the slide deck, you remove the performance. The conversation becomes the medium.
What's another example? You mentioned climate.
The Petersberg Summer School on Climate Policy ran from two thousand nine to twenty nineteen in Bonn. Twenty-five climate negotiators annually — from developed and developing countries — meeting in a residential setting for a week. It was credited with breaking the deadlock on the loss and damage mechanism in the Paris Agreement.
Loss and damage was the most contentious issue in the entire Paris process. Developed countries didn't want to acknowledge liability for climate damages, developing countries insisted on it. That deadlock nearly tanked the whole agreement.
The Petersberg format created a space where negotiators could have off-the-record conversations that weren't possible in the formal UNFCCC sessions. In a formal negotiating room, you're speaking for the record, to your capital, through the media. At Petersberg, you could say: "Look, here's what my ministry actually needs to be able to sell this domestically. What do you need?" That's the kind of exchange that produces breakthroughs.
The difference between "what is my government's position" and "what does my government actually need." Those are not the same thing, and you can only have the second conversation in a trusted, off-the-record setting.
That's the mechanism the summer school model enables. It's not that the format is magic — it's that the format removes the barriers to the conversation that actually needs to happen.
You mentioned a third example — the McDonnell Academy at Washington University.
The McDonnell International Scholars Academy runs what they call a policy lab format. It's not called a summer school, but it follows the same design principles. They've produced concrete legislation in twelve countries. The one I find most interesting is Rwanda's drone delivery framework for medical supplies.
Rwanda's drone delivery system is genuinely world-leading. They were doing routine medical drone deliveries years before anyone else. And the policy framework for that came out of a McDonnell lab?
The lab brought together Rwandan health ministry officials, engineers from Zipline, regulatory experts, and logistics specialists for an intensive residential workshop. They didn't write the legislation in the room, but they produced the design principles and the regulatory scaffolding that the legislation was built on. The key insight that emerged was that you don't regulate drones as aircraft — you regulate them as a medical supply chain. That reframing changed everything.
That's a beautiful example of what these gatherings do. They don't just produce text — they produce reframings. A drone isn't an aircraft, it's a supply chain node. Once you see it that way, the regulatory path becomes obvious. Before the workshop, nobody in the room had that frame.
That's the thing a conference panel would never produce. A panel gives you three people making prepared remarks, maybe ten minutes of Q and A, and then coffee. There's no mechanism for collective reframing.
Alright, so we've established that the model works and has a track record. Now let's get into the practical part — the facilitator's playbook. Because the prompt is really asking: how do you actually do this? And most people who try will get it wrong.
Let me walk through it step by step, because the failures are predictable and preventable. Step one is scoping, and this is where most summer schools die before they start. The most common failure mode is an overly broad topic.
Give me an example of too broad.
"How to reform the World Health Organization's emergency response protocol." That's a year-long commission topic. Thirty people cannot make meaningful progress on that in five days. It's too big, too vague, too many sub-problems. The "Goldilocks test" is: the challenge must be narrow enough that a group can make real progress in five days, but broad enough that no single participant already knows the answer.
What's the Goldilocks version of the WHO example?
"How to reduce the WHO's outbreak alert-to-response time from seventy-two hours to twenty-four hours in low-income countries." That's specific. It has a metric. It has a geographic scope. It's a problem where you can actually prototype solutions. And nobody in the room will have the complete answer, because if they did, they would have implemented it already.
The metric is crucial. If you can't state the problem as a measurable gap, you haven't scoped it properly.
The scope should also specify what's out of bounds. If you're doing the WHO alert-to-response problem, you might say: "We're not redesigning the WHO's governance structure. We're not debating funding models. We're focused on the operational pathway from alert to response." Those boundaries are liberating, not limiting. They let people go deep instead of wide.
Step two — who's in the room?
This is where you should spend forty percent of your preparation time. The rule of thumb I've seen from experienced facilitators is three-two-one: for every three academics, recruit two policymakers and one practitioner — someone who has actually implemented policy on the ground.
Why that ratio?
Because academics bring analytical depth and evidence. Policymakers bring institutional knowledge and political realism. Practitioners bring ground truth. If the room is all academics, you get elegant models that don't survive contact with reality. If it's all policymakers, you get incrementalism. If it's all practitioners, you get war stories without synthesis. The ratio forces productive tension.
You said forty percent of prep time on recruitment. That sounds absurdly high.
It's the single most important design decision. The Salzburg Global Seminar spends months on participant selection for each session. They use what I've heard described as the "airport test" — would you be happy to be stuck in an airport for six hours with every single participant? If someone fails that test, don't invite them, no matter how impressive their CV is.
The airport test is a good heuristic. It's screening for something specific — not likability, exactly, but something closer to intellectual generosity. You don't want to be stuck with someone who's going to dominate, or someone who's going to withdraw, or someone who's going to treat the whole thing as a networking opportunity.
There's another layer that the best summer schools get right: avoid the usual suspects. Actively recruit from the Global South. Bring in people from non-traditional disciplines — a behavioral economist for a housing policy summer school, an anthropologist for a tax policy discussion. And crucially, include junior talent. The people who will be running ministries in fifteen years. The Salzburg Global Seminar has an alumni network of over thirty-five thousand people across a hundred and seventy countries, and a documented policy impact rate of twenty-three percent — meaning nearly a quarter of their sessions led to measurable policy change within five years. That network effect is built by investing in emerging leaders.
The twenty-three percent number is worth pausing on. One in four sessions produces a measurable policy change. That's an extraordinarily high hit rate for something as messy as policy influence.
It's remarkable. And it's not because the sessions are brilliant — though many are. It's because the relationships formed during the week persist for decades. The white paper might be forgotten, but the WhatsApp group isn't.
Alright, step three. You've got your scope and your participants. Now what happens during the week?
The arc of the week is critical. The standard design that experienced facilitators use is a five-day structure. Day one: problem framing. No solutions allowed. You spend the entire first day making sure everyone agrees on what the problem actually is. Day two and three: divergent thinking. Brainstorming, small-group work, expert provocations, field visits if possible. Day four: convergent thinking. Prototyping, trade-off analysis, narrowing down options. Day five: output drafting. A white paper, a policy brief, a pilot proposal — something concrete that exists by dinner on the final day.
No solutions on day one. That's harder than it sounds. People show up with their pet solutions. They've been thinking about this problem for years. Telling them to sit on their hands for a full day while the group frames the problem is almost physically painful for some personality types.
That's exactly why it's necessary. If you let solutions into the room on day one, the rest of the week becomes an advocacy contest. Everyone's defending their pre-existing idea instead of building something together. The day-one problem-framing session forces people to surface their assumptions and negotiate a shared diagnosis before they start prescribing.
Each day should have a homework assignment?
Something that builds toward the final output. On day one, the homework might be: "Write one paragraph describing the problem as you now understand it, incorporating perspectives you heard today that you hadn't considered before." On day three, it might be: "Draft a one-page outline of your preferred solution with its three biggest risks." These small deliverables keep momentum and prevent the "we'll figure it out tomorrow" drift.
What about the empty chair technique you mentioned?
This is a specific technique for preventing groupthink. You invite two or three "critical friends" — skeptics, journalists, opposition politicians — for a single session, usually on day three or four, specifically to stress-test the emerging ideas. They're not there for the whole week. They parachute in, hear what the group has developed, and spend ninety minutes trying to break it.
That's the role of the designated antagonist. Every good workshop needs one, but if they're in the room the whole week, they poison the atmosphere. Bringing them in for a single session gives you the benefit of the criticism without the social cost.
It adds credibility to the final output. When you publish the white paper, you can say: "This was stress-tested by X, Y, and Z, who were invited specifically to challenge our assumptions." That's a stronger claim than "we all agreed with each other for five days.
Let's talk about recurrence. The prompt asks whether these can be annual events — a kind of truncated think tank — and how that differs from an annual conference.
The most successful summer schools are indeed annual, but with a rotating theme. The Petersberg Climate Summer School ran for a decade with a different sub-topic each year. The Salzburg Global Seminar runs ten to twelve sessions per year, each with a completely different cohort and topic. The "annual truncated think tank" model works when there's a permanent secretariat that tracks implementation between gatherings.
The secretariat is the continuity. The participants rotate, or at least partially rotate, but the institutional memory lives in the organizing team.
That's the key difference from an annual conference. A conference measures success by attendance. A summer school measures success by policy adoption rate. A conference has parallel tracks. A summer school has a single track with full-group plenaries. A conference is about information dissemination. A summer school is about relationship building and co-creation. They're fundamentally different activities that happen to share the word "gathering.
The parallel track thing is underrated as a design distinction. Parallel tracks mean participants self-segregate into their comfort zones. The health people go to the health track, the finance people go to the finance track. The summer school forces everyone into the same room for the same conversation. That cross-pollination is where the reframings happen.
It's exhausting in a productive way. You can't hide. You can't check email while someone drones through slides. You're in the room, and the room is small enough that your absence would be noticed. That social pressure to be present and engaged is part of the design.
What's the budget for one of these? Because the prompt is aimed at potential facilitators, and they need to know what they're signing up for.
A typical five-day residential summer school for thirty participants, including travel, accommodation, meals, facilitation, and materials, runs between fifty thousand and a hundred and fifty thousand dollars. The range depends on venue costs and how much travel you're subsidizing. If you're bringing people from the Global South, you need to cover their flights, and that adds up quickly.
That's not nothing, but it's also not astronomical. A mid-size foundation could fund several of these a year. The question is whether the return justifies the cost.
The RAND study I mentioned earlier — the three-point-two times idea-to-implementation rate — that's your return argument. If a hundred-and-fifty-thousand-dollar summer school produces a policy framework that influences billions in public spending, the ROI is off the charts. The problem is that it's hard to attribute policy change to a single gathering, which makes it hard to fund these through traditional grant mechanisms that demand measurable outcomes within a grant cycle.
That's the evaluation challenge, isn't it? Policy influence is diffuse and takes years. By the time the impact is measurable, the gathering that catalyzed it is a distant memory.
That's why the Salzburg Global Seminar's twenty-three percent impact rate is so impressive — they've actually done the longitudinal tracking. But most summer schools don't have the resources for that kind of follow-up. Which brings me to the accountability mechanism, which I think is essential and often overlooked.
The post-summer school piece.
The best summer schools build in a six-month follow-up where the group reconvenes virtually to check progress on commitments. The Bellagio Pledge model is particularly effective: before leaving, each participant commits to one specific action they will take in the next six months. It's public within the group, which creates gentle social accountability. And the six-month check-in is structured as "what did you do, what got in the way, what help do you need.
That's the difference between a memorable week and an actual intervention. Without the follow-up, you're just running an expensive retreat.
One thing I want to address directly, because the prompt asks about it: can this model work virtually?
Let me guess.
The short answer is no. The informal interactions are the magic ingredient. The conversation that happens at eleven PM over a glass of wine, the walk by the lake where two participants realize they've been working on complementary pieces of the same problem, the breakfast where a junior researcher asks a senior policymaker a question they'd never ask in a formal setting — none of that replicates on Zoom. There was a Virtual Bellagio pilot in twenty twenty-two, and the honest assessment from participants was that it was a useful discussion but it wasn't a summer school. The trust-building didn't happen.
The "eleven PM conversation" is doing a lot of work here. That's the Dunbar number effect, right? Groups of thirty to forty allow for genuine trust. You can't maintain a persona for five days in a residential setting. Eventually you're just yourself, and that's when the real work happens.
Robin Dunbar's work on social group sizes is directly relevant. Thirty to forty people is roughly the size of a hunter-gatherer band. It's the largest group where everyone can know everyone else as individuals, not as roles. A conference of five hundred people forces you into role-based interactions. A summer school of thirty people lets you interact as a person. That's the structural advantage.
The absence of an audience removes performative posturing. In a conference, you're always speaking for the benefit of the room, the Twitter audience, the people who might hire you. In a summer school, there's no audience. Everyone's a participant. The dynamic is completely different.
There's a Richard Titmuss quote that captures this perfectly. He said: "The best social policy is made in rooms where people are uncomfortable enough to change their minds." Not uncomfortable in a hostile way — uncomfortable in the sense of being challenged, of having your assumptions exposed, of realizing you don't have the answer you thought you had. That discomfort requires trust. And trust requires time, proximity, and privacy.
That's a great quote. And it points to something about the model that's worth naming explicitly: the summer school is a reminder that the best policy solutions come not from lone geniuses or large bureaucracies, but from small, diverse groups given the time and space to think together. That's almost subversive in an era that fetishizes both individual brilliance and institutional scale.
It's deeply subversive. It says the unit of policy innovation isn't the think tank or the commission or the white paper — it's the conversation. A specific kind of conversation, in a specific kind of setting, with a specific kind of structure. And if you get the structure right, the conversation does work that no individual could do alone.
Let me ask about a misconception I've seen. People hear "Bellagio" or "Ditchley" and think you need a villa on Lake Como to make this work. What's the reality?
The model works in any residential setting that provides isolation and informality. A university dormitory in the summer, a retreat center, a repurposed hotel — the key is that participants are removed from their daily contexts and can't easily leave. Luxury is not the point. In fact, overly luxurious settings can undermine the work by making it feel like a vacation. The Sussex summer school in nineteen sixty-four was held in university accommodations that were, by all accounts, perfectly adequate and not particularly comfortable.
The Sussex dorms as the birthplace of the British welfare state's safety net. There's something almost beautiful about that. Another misconception: that these are just elite networking events.
They are structured co-creation workshops with a defined output. They're not social mixers. The most impactful ones deliberately include junior professionals, activists, and frontline practitioners specifically to challenge groupthink. If you're only inviting directors and ministers, you're doing it wrong. The Salzburg model explicitly reserves spots for what they call "emerging leaders" — people in their late twenties and early thirties who will be shaping policy in a decade.
The misconception that the output — the white paper, the policy brief — is the most important thing?
The relationships and trust built during the week often have more long-term impact than the document produced. The white paper might sit on a shelf, but the network persists. I've seen evaluations where participants, five years later, said the most valuable thing they got from the summer school was a collaborator they still work with, not the output document.
Which is a hard thing to put in a grant report. "We spent a hundred thousand dollars and produced... a WhatsApp group." But that WhatsApp group might be the most valuable deliverable.
That's the tension in funding these things. Foundations want outputs. The real value is in outcomes, which are harder to measure and take longer to materialize.
Let's shift to the forward-looking piece. The prompt is implicitly asking: what's next for this model? And I want to flag two developments. One is the citizen summer school — bringing together ordinary citizens, not just elites, to co-design policy.
The Irish Citizens' Assembly is the obvious reference point. It brought together ninety-nine randomly selected citizens to deliberate on constitutional questions, including the abortion referendum. It's not quite a summer school — it's a different format, a citizens' assembly — but it's a cousin. The principle is the same: give a diverse group of people time, information, and structured facilitation, and they can produce thoughtful policy recommendations that representative bodies can't or won't.
The second development is the question of whether AI-enabled asynchronous collaboration could ever replicate some of what a summer school does. You mentioned the Virtual Bellagio pilot was disappointing. But the technology is improving.
I'm skeptical. The trust-building that happens in a residential setting depends on presence — physical co-location, shared meals, informal moments, body language, the ability to read a room. AI can facilitate structured deliberation, but it can't replicate the eleven PM conversation. What might work is a hybrid model: a short in-person kickoff — say, three days — followed by structured asynchronous collaboration, with a final in-person session to converge. That captures some of the trust-building while reducing cost and time commitment.
The in-person component isn't optional, but it might be compressible.
That's my read. But we're in early experimental territory. The evidence isn't there yet.
Before we wrap up, let's hit the practical takeaways for someone who's listening and thinking: I want to organize one of these.
First, start with the output, not the topic. Define what "done" looks like on day five — a ten-page policy brief, a pilot proposal, a joint op-ed — and work backward. That discipline prevents scope creep and keeps the week focused.
The output defines the process, not the other way around.
Second, spend forty percent of your preparation time on participant selection and vetting. Use the airport test. Avoid the usual suspects. And if you're not sure about someone, don't invite them. One difficult participant can derail an entire week.
Build in the post-summer school accountability mechanism. The Bellagio Pledge, the six-month check-in — whatever format you use, don't let the week end without each participant making a specific commitment. The summer school isn't the intervention. The summer school plus the follow-through is the intervention.
For listeners who want to attend one rather than organize one: what should they look for?
Look for summer schools that publish their alumni's policy impact. The Oxford Policy Summer School publishes an annual impact report — that's a good sign. Avoid any summer school that charges more than five hundred dollars for tuition. The best ones are fully funded by foundations. If someone's trying to make money off you, they're not running a summer school — they're running a business.
The tuition test is a good litmus filter. If it costs two thousand dollars to attend, it's a conference with better branding.
One last thought. The summer school model has been producing results for sixty years, and it's still not the default way policy gets made. Most policy development still happens through commissions, consultations, and conferences — formats that are demonstrably less effective at producing actionable ideas. Why hasn't the summer school model scaled?
Partly because it's harder to do well. It requires design discipline, facilitation skill, and a willingness to invest in relationships over outputs. Partly because the conference industrial complex has its own momentum — venues, sponsors, professional associations, the whole ecosystem. And partly because the people who control policy budgets are often the same people who benefit from the existing formats. A minister gets more visibility from giving a keynote at a conference of five hundred than from spending a week as a co-equal participant in a summer school of thirty.
The format that's better for policy is worse for personal brand-building. That's a real structural barrier.
But the evidence is accumulating. The RAND study, the Salzburg impact data, the concrete policy outcomes from Bellagio and Petersberg and Sussex — the case is getting harder to ignore. If you're working on a policy problem that feels stuck, a summer school could unlock it. The format is proven. It just requires discipline to execute well.
That's the note to end on, I think. The summer school is a proven tool that most people in policy have never used. It's not a conference. It's not a retreat. It's not a think tank. It's a specific, structured format for co-creating solutions — and the evidence says it works better than the alternatives.
And now: Hilbert's daily fun fact.
Hilbert: Diatomaceous earth from a deposit on São Tomé was traded as far as the Roman Empire, where it was prized as a pure white pigment for frescoes — its brilliance came from fossilized diatom shells, which are essentially microscopic glass.
Microscopic glass on Roman walls.
This has been My Weird Prompts. Thanks to our producer Hilbert Flumingtop. If you enjoyed this episode, leave us a review wherever you listen. We're at myweirdprompts dot com. Until next time.
