Moving At The Rhythm Of Transformation: Designing Intentionally In Tune With Learning

By Federico Bortoletto & Caroline Raundahl

At Kaospilot, we’ve always been rethinking how learning happens. This semester we’re experimenting with a weekly rhythm that puts preparation, integration, and rest on equal footing with input and visible work. This article shares what we changed, what we’re noticing, and why unscheduled time might be some of the most important learning time of all.

“Why do we have unscheduled time on Friday afternoon? Shouldn’t we be doing something?”

The question came up in the corridors during our first week back in January. A student, genuinely concerned, wondered if the new weekly schedule we’d introduced meant they were somehow getting less. Less input. Less value. Less education.

It’s the question we expected – and it reveals exactly why we needed to redesign our week in the first place.

The experiment began with a simple provocation that many of us know but rarely design for: what if the real obstacle to deep learning isn’t lack of content or even context, but the pace at which we deliver it?

When “productive” becomes the problem

For years, students at Kaospilot have been telling us the same thing: something isn’t working. The weekly structure itself wasn’t serving them. There was an intention for preparation and integration, but in practice the week was mostly lectures and input, with any deeper work pushed outside scheduled hours or left to each team – and each student – to figure out. Back-to-back sessions would squeeze out the breathing room. Integration would happen when there was time, if there was time. Preparation would compete with everything else demanding attention.

The feedback was consistent: we need more deliberate time for reading and preparation before lectures, dedicated space for integration and sense-making, protected time for teamwork and project development, and a rhythm that prevents burnout and supports sustained learning. Not just occasionally. Structurally.

Our pedagogy has always been rooted in agency – in inviting students to take responsibility and ownership of their learning, to find their own ways of preparing, integrating, and applying what they meet here. But in this case, we realised that leaving it entirely to individual and team initiative wasn’t enough. We needed to intervene at the level of structure and create shared, protected spaces where that agency could breathe.

The design: what we’re actually doing

In January, we introduced a new weekly structure as a semester-long prototype, co-designed by students, team leaders, and staff. It’s a simple shift with profound implications: a week shaped not by how much we can fit in, but by how well we can prepare, engage, integrate, and land.

Every day starts at 9:30 AM. We’re honoring different chronotypes and recognizing that the hours before scheduled time are valuable – for connection, project work, deepening relationships, or simply arriving at the day in a way that suits different needs.

Scheduled learning happens in 45-minute blocks, ending by 2:45 PM. After that, the afternoon is open by design: time for connection, collaborative project work, individual study, or whatever the learning is calling for in that moment. The point isn’t to prescribe what happens, but to protect the conditions in which meaningful work and integration can occur.

Mondays begin with a community gathering across all teams, then move into team-held preparation time. This isn’t just socializing or catching up; it’s orienting. We review pre-readings, clarify why particular practitioners are coming, and make sense of how this week’s learning connects to ongoing projects and the broader arc of the semester.

Tuesdays, Wednesdays, and Thursdays are for input and active engagement. These three days hold the practitioners, workshops, and lectures – around 15–16 hours of intensive, participatory learning with diverse perspectives and approaches. It’s the kind of active, relational learning Kaospilot is known for, but held within a clearer rhythm.

Fridays are for landing. In the morning, each team gathers to connect patterns across different inputs, see how this week nests within the semester and the three-year journey, and offer feedback that helps team leaders adjust what’s needed. This is where weekly inputs start to crystallize into coherent capability. Friday afternoon is protected time: individual study, deep project work, portfolio development – the slower, less visible work that allows learning to compost.

What we’re learning (so far)

A month in, some things are already clear. The learning field feels more attuned and generative – with our whole learning community, internal and external, arriving more present, more grounded, and more able to engage. The resistance we anticipated in December has largely dissolved; most have embraced it.

But this is still a prototype. We’re learning as we go – how to hold this container generatively, what it asks of us as staff and team leaders, where the design needs adjusting. It’s not perfect, and we don’t expect it to be. That’s the point.

And yet there’s still friction. A nagging feeling, for some, that unscheduled time equals unproductive time. That if they’re not in a session, receiving input or producing something visible, they’re somehow not really learning.

Hartmut Rosa names one part of this dynamic “social acceleration”: the way modern life speeds everything up, compressing time and leaving less and less room for connection and reflection. His counter-concept is “resonance” – deep, alive connection that needs unscheduled time to emerge, the kind of connection that cannot be manufactured, optimized, or squeezed into 45-minute slots.

Franco Berardi diagnoses another dimension: semiocapitalism. A system that tries to extract value from every fragment of mental time and attention, turning even “free” time into an opportunity to optimise, improve, or produce – or extract. Even rest becomes another form of productivity. In that context, a free Friday afternoon can feel wrong – not because it doesn’t work, but because it doesn’t fit the script.

So, we’re not just redesigning a weekly schedule. We’re participating in redesigning the kinds of futures our students can imagine and rehearse together.

Designing Rhythms for Ontological Change

Arturo Escobar reminds us that “we design our tools and then our tools design us.” This is ontological design: whenever we design anything – a curriculum, a timetable, a classroom – we are also designing ways of being, relating, and knowing. The structural designs we create, shape who we become and the culture we inhabit together.

The old rhythm – continuous input, back-to-back sessions, no breathing room – wasn’t neutral. It was quietly reinforcing a particular kind of learner: someone who can absorb and process quickly, stay sharp under pressure, and produce visible outputs on demand. Those are valuable capacities. But on their own, they are not enough for the kind of transformation work we’re preparing people for, nor do they honor the diversity of learning tempos and styles present at Kaospilot.

The new rhythm is inviting for something different. It’s creating conditions for learners who prepare thoughtfully, engage deeply, integrate across difference, and trust that not all valuable work is immediately visible. It’s supporting practitioners who understand that transformation happens in the spaces between inputs – in the slow, messy time it takes for patterns to emerge – and who can tolerate not knowing for a while.

This is where Bayo Akomolafe’s notion of “radical incompleteness” becomes a practice, not just a concept. Modernity, he suggests, “thinks in terms of categoricity, completion, closed borders, closed loops.” But things are constantly blending into each other. Relations come before things. “Things only gain their ‘thinginess’ from relationship.” Emergence, for Bayo, is “how things are constantly inquiring into their exquisite, orgasmic, non-completeness.”

That is what we are rehearsing in the weekly structure. Not completion. Not cramming in maximum input per hour. Not optimizing every moment. Instead, we are cultivating the conditions for transformation: space, breathing room, time for things to compost and connect in ways we can’t predict or control.

The Monday preparation is not just “getting ready” for Tuesday’s workshop. It is creating relational context – between the learner and the material, between emerging questions and the practitioner’s approach, between this week’s input and everything else a student is carrying, and between us as a learning community. The Friday integration is not just “reviewing what we learned.” It is an invitation for patterns to emerge that we couldn’t have planned for.

This is how transformation works in the field. We don’t get to control all the inputs. We don’t get to optimise every interaction. We need the capacity to prepare, engage, integrate, apply – and then do it again, learning from what emerges along the way.

The weekly rhythm is our attempt to mirror the actual rhythm of transformation practice.

When the body’s knowledge and the brain’s data align

We could talk about the neuroscience of spaced learning – how it increases neural pattern reactivation in the prefrontal cortex and produces significant improvements in long-term retention compared to cramming. We could cite studies showing that learners who engage with material before class perform substantially better than those who arrive unprepared. We could reference research on cognitive load and memory consolidation and why shorter learning blocks with breaks align with how our brains process information.

And all of that is true. Research strongly supports this approach.

But honestly? The research isn’t why we did this. We did this because for years, students have been telling us that something wasn’t working. Because exhaustion and overwhelm don’t produce the kind of practitioners we’re trying to develop. Because transformation work requires capacities that we can’t build when we’re always in input mode.

The research just confirms what our bodies and nervous systems have been telling us for quite some time: deep work requires a different beat.

This is a prototype

Here’s what matters: we’re approaching this the way we invite education spaces to approach design work. Prototype. Test. Gather feedback. Iterate.

We’re running this structure from January until June, then we’ll evaluate together (students, staff, lecturers) to understand what needs adjusting. This isn’t the final answer. It’s an inquiry into what serves learning, well-being, and the development of transformation practice.

Some things we’re already noticing might need adjustment. Some things are working better than we imagined. And some things we won’t fully understand until we’ve lived with this rhythm for longer.

This is part of how Kaospilot works: continuously adapting, evolving, inquiring. Not because we have all the answers, but because we’re committed to staying responsive to what’s needed, to what’s working, to what wants to emerge.

To be continued

This is the first of two articles. In June, when we complete this semester-long prototype, we’ll return with reflections on what we’ve learned, what we’re adjusting, and what emerged that we didn’t predict. We’ll share feedback from students, staff, and lecturers – the full picture of what this rhythm made possible and where it fell short.

Because this is how prototypes work: you design, you test, you learn, you iterate. And then you share what you’re learning with others who might be experimenting with similar questions.

See you in June!

An invitation

If you’re an educator reading this, maybe you’re recognizing something familiar: the tension between providing “enough” content and creating space for actual learning; the pressure to fill every hour with visible productivity; the students who’ve internalized the logic of optimization so deeply they can’t quite trust that unscheduled time might be the most valuable learning time of all.

If you’re a student or prospective student, maybe you’re feeling some relief. Or maybe some anxiety. Both make sense.

If you’re part of the broader transformation education community, maybe you’re experimenting with similar questions about learning structure design, sustainable performance, and what it takes to develop practitioners who can work with complexity and emergence.

We’d love to hear from you. What rhythms are you experimenting with? What friction are you encountering? What’s emerging that you didn’t predict?

Because this is the work, isn’t it? Not just teaching about transformation but transforming how we teach. Not just talking about emergence but designing for it. Not just training people to be productive but developing the capacity to work at the rhythm that transformation requires.

This weekly structure design is more than a timetable exercise; it is a rehearsal for life in a complex world – a way of practicing how to move with uncertainty, honor limits, and still stay in relationship with what matters.