Poetry as Design: What building schools in the cloud has taught me about governance, trust and relational infrastructure
There is a particular kind of scepticism that arrives when you pair the word poetry with the word design...
Poetry, the thinking goes, belongs at the edge of serious work: the epigraph at the start of a report, the flourish in a speech, the humanising line before the actual business begins.
Design is the serious work: the systems, the processes, the architecture, the safeguarding, the compliance, the delivery model.
Poetry decorates.
Design builds.
I have come to believe this is exactly wrong.
Over the past several years, I have helped build and shape multiple schools in the cloud: online, hybrid and distributed learning environments for young people who need education to be more flexible, more relational, more humane and more structurally coherent than conventional models often allow.
Some have served neurodivergent learners. Some have supported young people outside mainstream education. Some have been built with local authority commissioning in mind. Some have emerged from specialist provision, alternative provision, tutoring infrastructure, or wider system-change work.
Each build has been different.
But the pattern beneath them has become increasingly clear.
A school in the cloud is not a website with lessons attached. It is not a timetable delivered through video calls. It is not a digital copy of a physical school.
It is a relational system.
And relational systems do not hold because they are well-branded. They hold because their rituals, roles, technologies, policies and human rhythms cohere under pressure.
Not poetry as ornament. Poetry as compression. Poetry as memory. Poetry as the form a principle takes when it needs to survive a difficult meeting, a safeguarding concern, a platform failure, a parent in distress, a young person who has stopped attending, or a practitioner who is quietly burning out.
A maxim is not a slogan.
A good maxim is a portable design law.
It tells you what to protect when the system starts to drift.
The recursive field
The most important thing I have learned is that no school in the cloud can be built alone.
It may have a founder. It may have a leadership team. It may have a platform. It may have policies, budgets, staff and launch timelines.
But the real intelligence of the build comes from the recursive field around it.
For me, that field is increasingly held through the Novus Learning Network, via The Novacene Collective: a growing community of educators, school-builders, technologists, safeguarding leads, researchers, commissioners and system thinkers who are learning aloud together.
This matters more than I can overstate.
Every school I help build now teaches the next one. Every platform failure sharpens the next procurement process. Every safeguarding ambiguity strengthens the next governance layer. Every conversation with a practitioner changes how I think about workload, presence and trust. Every parent's anxiety tells me something about the communication architecture. Every learner who cannot yet attend tells me where the system is still too brittle.
That is recursion.
Not repetition or scaling a template.
Recursion: a living system learning from itself, through relation, across contexts.
The Novus Learning Network matters because it prevents each school from becoming a closed container. It creates a commons where insight can travel without flattening difference. The aim is not to make every provision the same. The aim is to let each build become wiser because the others exist.
The school in the cloud is not one institution. It is an emerging design field. And I am about to begin the most ambitious build yet.
Not because it will be the biggest. Bigger is often a lazy ambition.
It is ambitious because the conditions are more complex, the stakes are higher, and the need for coherence is sharper. It will require everything the previous builds have taught me: about safeguarding, governance, AI, platform architecture, attendance, practitioner trust, commissioner confidence, parent communication, neurodivergent access, and the quiet emotional physics of learning after rupture.
So this piece is not about one school.
It is about what building several schools in the cloud has taught me.
The field laws
The verse-al maxims are a set of working field laws. They come out of a decade of watching organisations succeed and fail at scale: schools, alternative provision, online learning communities, safeguarding-heavy services and emerging AI-enabled systems.
They sit alongside a core claim: intelligence is relational, not merely nodal.
What happens between people, systems, meaning, memory and trust is often more structurally important than what sits inside any one of them.
That is especially true in cloud-based education.
A physical school has walls, corridors, bells, offices, assemblies, staffrooms and playgrounds. Some of that architecture creates belonging. Some of it creates harm. But it does create an ambient field.
In a school in the cloud, almost none of that exists by default.
Presence has to be designed.
Trust has to be designed.
Ritual has to be designed.
Safeguarding has to be designed.
Belonging has to be designed.
Even silence has to be designed, because a camera-off learner in an online classroom may be safe, overwhelmed, disengaged, masking, listening deeply, or gone entirely.
The system has to know the difference.
That is why maxims matter. They are not decorative language. They are diagnostic instruments.
These are some of the field laws that now shape how I build.
A metaphor that does not connect real ground to real ground is theatre, not structure.
Schools are full of beautiful language: inclusion, belonging, personalised learning, student voice, wellbeing, innovation.
The question is always: where does it land?
If a value cannot be seen in a timetable, a staffing model, a platform choice, a safeguarding workflow, a budget line, a lesson rhythm or a parent communication, it has not landed.
It is still theatre.
In every cloud-school build, I now ask: what does this principle become on a wet Tuesday morning when a tired practitioner opens the system and a learner does not arrive?
If the answer is unclear, the bridge has not landed.
Even silent attendance transmits symbolic charge. Absence drains it.
This may be the single most misunderstood part of online education.
Too many people still imagine that digital learning is primarily a content delivery problem. It is not. It is a presence problem.
For young people who have become disconnected from education, the arrival of a real adult at a predictable time is not a nice extra. It is the intervention.
A live session is not valuable simply because information is exchanged. It is valuable because it says:
You were expected.
You were noticed.
You were not too much.
You were not forgotten.
In a school in the cloud, presence must be treated as infrastructure, not personality.
That means staffing ratios, session design, supervision rhythms, communication protocols and platform choices all have to protect the conditions under which presence can be felt.
A login is not a relationship.
Trust is not built through grand gestures. It compounds through small things done well and on time.
Parents do not trust a school because of the prospectus.
Commissioners do not trust a provider because of a launch event.
Learners do not trust a practitioner because the website says the provision is trauma-informed.
Trust comes from the session that starts when it said it would. The follow-up that arrives. The safeguarding note that is logged. The invoice that matches the actual provision. The parent update that is sent before anxiety spikes. The practitioner who remembers what happened last week.
Cloud schools live or die by rhythmic reliability.
This is not glamorous work. It is not usually the part that gets celebrated.
But it is the load-bearing part.
Expression without structure dissolves into noise. Hold the field first, then release the emotion.
This one has become non-negotiable.
The temptation in every new school build is to begin with the exciting work: the curriculum, the pedagogy, the learner voice, the creative offer, the story.
But if the container is weak, the beautiful parts become unsafe.
The container is safeguarding. Data protection. Role clarity. Incident protocols. Consent boundaries. AI governance. Escalation routes. Staff supervision. Attendance logic. Platform permissions. Records management.
These things can look dry from the outside.
They are not dry.
They are the vessel.
A cloud school without containment becomes a blur of goodwill, overwork and unmanaged risk.
A cloud school with containment can become spacious, humane and alive.
Numbers lag fields.
By the time attendance data looks bad, the relationship has usually been drifting for weeks.
By the time staff turnover becomes visible, the practitioner field has already been under strain.
By the time complaints arrive, the communication architecture has often been failing quietly for some time.
Metrics matter. Of course they do. But they are late signals. The field speaks earlier.
It speaks in the tone of session notes. In the kind of questions parents ask. In whether staff cameras are off in meetings. In whether people stop raising small concerns. In whether learners disappear gradually rather than suddenly. In whether leaders become addicted to dashboards because they have lost contact with the atmosphere.
Cloud schools need data.
But they also need field literacy.
The spreadsheet should confirm what the relational field has already begun to tell you.
Be unsentimental about the pattern; be gentle with the person.
This is essential in system-building.
Sometimes the truth is hard. A beloved tool is not compliant. A role has become incoherent. A process that once worked no longer scales. A warm habit creates safeguarding ambiguity. A flexible arrangement has become structural isolation. A platform is convenient for adults but inaccessible for learners.
These things have to be named.
But people are not problems.
The work is to separate the pattern from the person: to be clear enough to protect the system and humane enough not to shame the people who have been holding it together.
In education, too much harm is caused by avoiding difficult truths until resentment does the talking.
Brutal clarity with soft edges is a leadership discipline.
If it works for the margin cases, the core will thrive.
This is one of the clearest lessons from building for neurodivergent learners, anxious learners, attendance-fragile learners, traumatised learners and young people who have already been failed by multiple systems.
Do not design for the average learner.
The average learner is a statistical convenience, not a child.
Design for the learner with the slow internet connection, the noisy house, the demand avoidance, the sensory overwhelm, the parent who is exhausted, the interrupted educational history, the fear of being seen, the brilliant mind hidden behind refusal.
If the system works there, it will work almost everywhere.
If it only works for the compliant, resourced, verbally confident learner with stable attendance and adult support at home, it is not inclusive.
It is selective by architecture.
Policies must be legible as rituals.
If a rule cannot be enacted, felt, practised and checked, it is not governance. It is decoration.
This is where poetry and compliance meet.
A policy that nobody can remember will not protect anyone at 4pm on a Friday.
A safeguarding process buried in a forty-page document will not help a new practitioner make a sound decision under pressure.
An AI policy that uses abstract language about innovation and ethics but gives staff no practical decision route is not governance. It is reputational theatre.
Good governance has rhythm.
It has memorable questions. Clear thresholds. Refusal routes. Escalation paths. Audit trails. Shared language. It can be taught, rehearsed and used.
The poetry makes it portable.
The teeth make it real.
Confident answers that foreclose wonder are drift disguised as progress.
Every school build needs closure: policies published, roles agreed, platforms selected, timetables fixed, fees set, inspection evidence prepared.
That is the work.
But closure is not the same as coherence.
Closure says: we have finished.
Coherence says: we are aligned enough to move, and alive enough to keep learning.
A school in the cloud should never pretend to be finished. The learners will change it. The staff will change it. The technology will change it. Regulation will change it. The world will change it.
The discipline is not to freeze the model.
The discipline is to maintain coherence while the model learns.
What distributed provision teaches about adults
The next set of maxims emerged from working with distributed teams.
They are less about learners and more about the adults who hold the system.
That matters, because every learner-facing promise eventually cashes out in adult capacity.
If practitioners are isolated, overloaded, unclear, under-recognised or misaligned, the learner experience will degrade no matter how beautiful the model looks on paper.
To move in the same direction is not to become the same thing.
This is crucial in ecosystem work.
A cloud school may sit alongside local authorities, charities, specialist providers, tutoring organisations, mainstream schools, parents, researchers, technologists and policy frameworks.
The temptation is to merge everything into one voice, one brand, one pipeline, one story.
That can look efficient.
It often creates turbulence.
Healthy ecosystems need distinct streams moving coherently in the same direction. The school is not the commissioner. The commissioner is not the parent. The parent is not the practitioner. The practitioner is not the platform. The platform is not the pedagogy.
Fusion creates role confusion.
Coherence protects difference.
In any delivery organisation, there is one role that holds the structural weight.
In cloud schools, that role is usually the practitioner.
Everything else is scaffolding.
The platform, policies, leadership structure, dashboards, curriculum documents, onboarding flows and quality assurance systems exist to support the moment where a practitioner meets a learner and something becomes possible.
If the system makes that moment harder, the system is wrong.
This is not sentimental. It is structural.
A school can survive a clumsy document. It can survive a platform inconvenience for a while. It can survive an imperfect process.
It cannot survive the steady erosion of practitioner capacity.
Never move the load-bearing wall without knowing what falls.
Occasional appreciation is not enough.
Distributed teams need rhythmic recognition because they do not receive the ambient signals of being part of a place.
There is no staffroom glance. No corridor joke. No shared kettle. No physical sense of “we are in this together”.
If recognition is left to chance, the loudest moments dominate: crisis, correction, urgency, complaint.
So recognition has to become ritual.
A weekly acknowledgement. A genuine feedback loop. A practitioner voice channel that is actually read. A supervision structure where people are seen before they are depleted. A termly rhythm of reflection that makes contribution visible.
Not performative praise.
Predictable recognition.
The rhythm is the recognition.
A workforce model designed for flexibility can drift into structural isolation.
This is one of the great risks of online education.
Working from home can be liberating. It can also become lonely, disembodied and emotionally leaky.
Flexible provision can attract brilliant practitioners who need autonomy, but autonomy without connection becomes abandonment.
The design challenge is to protect both.
Flexible in location.
Flexible in rhythm.
Connected in practice.
Held in community.
A distributed workforce needs a commons: not a document graveyard, not a performative chat channel, but a living professional field.
Without that, flexibility becomes a polite word for isolation.
You cannot extract mission-aligned behaviour from people who were not recruited, inducted or supported for it.
Recruitment is not admin.
It is the first act of culture.
Every cloud-school build has taught me this more sharply. The right practitioner can make an imperfect system work while the system matures. The wrong practitioner can make even a strong model incoherent.
This does not mean recruiting clones. Quite the opposite. Healthy alignment allows for difference.
But there must be shared orientation: towards the learner, towards safeguarding, towards relational practice, towards reflective professionalism, towards the specific demands of working online.
Misalignment compounds.
So does alignment.
Choose carefully at the threshold.
Why maxims travel
A fair question is: why maxims at all?
Why not just write policies, handbooks, onboarding documents, training modules and project plans?
The answer is that we need all of those.
But they are not enough.
Policies do not always survive contact with urgency.
Handbooks are not always open when the difficult decision arrives.
Training can fade.
Project plans become obsolete the moment reality starts talking back.
Maxims travel differently. They are compressed enough to remember. Strong enough to interrupt drift. Flexible enough to apply across contexts. Sharp enough to diagnose a problem before it becomes a crisis.
They work because they sit between poetry and protocol.
A maxim can become a question in a leadership meeting.
A line in an induction.
A test for platform procurement.
A prompt in supervision.
A phrase a practitioner remembers when deciding whether to push, pause or contain.
A way of noticing that the system is beginning to betray its own values.
This is why I call poetry a design technology.
Not because it makes systems prettier.
Because it makes principles portable under pressure.
What several schools in the cloud have taught me
After several builds, I no longer believe the central question is whether education should be online, hybrid or physical.
That argument is too crude.
The real question is whether the learning field is coherent.
A physical school can be profoundly incoherent. An online school can be deeply relational. A hybrid model can be either liberating or chaotic.
The medium does not guarantee the ethic. The architecture does not guarantee the relationship. The platform does not guarantee the presence.
We have to design for the relation itself.
That means asking harder questions.
Where does trust accrete?
Where does safeguarding live?
Where does adult judgment land?
Where does learner agency increase?
Where does the system notice drift?
Where can a child refuse?
Where can a practitioner pause?
Where can a parent understand what is happening?
Where can governance be enacted rather than admired?
Where does the metaphor touch the ground?
These questions apply in London, Lagos, Lisbon, Los Angeles, Lahore or anywhere else a school in the cloud might be built.
The regulatory frameworks will differ. The funding models will differ. The cultural context will differ. The field laws still matter.
Because wherever the school is, the human truths remain stubbornly similar: children need reliable adults; adults need coherent systems; trust needs rhythm; safety needs teeth; learning needs presence; and innovation without containment is just risk with better branding.
The commons we are building
This is why the Novus Learning Network matters.
Through The Novacene Collective, it creates a place where the learning from one build can inform another without imposing a single model.
It is not a franchise logic or a consultancy funnel. It is not a neat methodology pretending the world is simpler than it is.
It is a recursive commons for people building at the edge of education, technology, safeguarding and relational design.
A place to compare patterns, to test language, to share what broke.
A place to ask what held. A place to develop governance that practitioners can actually use.
A place to let the next school become wiser because the previous ones were honest.
That is the work now.
Not just building schools in the cloud. Building the field that helps them learn from one another.
Poetry as infrastructure
Poetry is not the opposite of rigour. It may be one of rigour's highest forms.
A good line carries structure. It compresses experience without flattening it. It can be remembered, tested, repeated, challenged and lived.
That is what the best design principles do too.
The poetry is the compression. The design is the teeth. Together, they become infrastructure.
And after several schools in the cloud, this is what I know:
The future of education will not be secured by platforms alone. It will be secured by the quality of the relational architectures we build around them.
By the rituals that make trust repeatable, the governance that can be enacted, the adults who stay coherent under pressure.
By the systems that learn recursively without losing their soul.
And perhaps by a few poems with teeth, carried carefully from one school to the next.
Kirstin Stevens is Director of The Novacene Ltd and steward of The Novus Learning Network. Her work focuses on schools in the cloud, AI governance, relational infrastructure and verse-al design. The verse-al maxims are a project of The Novacene Collective.
First published in Building Schools in the Cloud on LinkedIn, 19 April 2026.