A New Approach to Organizational Transformation
PAK versus KAP — Rethinking How We Learn and Lead Change
I once had the privilege of being taught and mentored by Jerry Sternin, a legendary ethnographer and pioneer in the co-development space. Jerry championed the idea of harnessing the creative power of users to devise better solutions for complex, ingrained problems. Rather than imposing external, technical fixes that often failed to take root, he worked from within — focusing on adoptable behaviors and practical experimentation instead of abstract theories or the assumption that knowledge must precede action.
Jerry’s philosophy revolved around a fundamental shift in learning approach: PAK versus KAP.
PAK: Practice → Application → Knowledge
PAK stands for Practice, Application, Knowledge — a learning model that flips the traditional hierarchy on its head. It begins with Practice, where hands-on experience demonstrates immediate value, instilling trust and hope within the team. Through Application, we extend what works, adapting tools to new contexts and challenges. Only then do we move into Knowledge, where reflection and theory help us understand why the approach works and how to evolve it further.
Sternin’s work in impoverished villages, war zones, and refugee camps proved that deep change doesn’t start with lectures or frameworks — it starts with doing. And it scales through insight, not instruction.
KAP: Knowledge → Application → Practice
In contrast, the traditional model — KAP — starts with Knowledge. We are taught theory first, shown examples of Application, and finally, if time and persistence allow, we reach Practice. This top-down approach often disconnects learners from immediate relevance, delaying the sense of mastery until much later — if at all.
Applying PAK in the Modern Enterprise
In my work with advanced organizations today — from large enterprises to fast-moving product teams — I’ve found that PAK isn’t just for fieldwork in extreme contexts. It’s just as essential inside corporate environments navigating transformation, AI adoption, and cultural change.
I begin with short, focused bursts of real work — tangible, human-centered design sprints around known organizational pain points. These are often “wicked problems” that cross silos, depend on collaboration, and resist easy solutions. By tackling just one of these problems through practical experimentation, teams experience a “P” moment: proof that change is possible, here and now.
This success builds momentum. With each Application, the organization becomes more confident, more aligned, and more fluent in its own design and innovation language. Eventually, we enter the Knowledge phase, where people begin to see patterns, internalize methods, and adapt frameworks to their own realities — not because they were told to, but because they’ve lived it.
From Behavior Change to Cultural Transformation
This method now extends far beyond innovation labs. I apply PAK in:
- Product and portfolio shaping, to align teams around real customer value rather than abstract KPIs.
- Innovation capability building, where we grow design maturity and create conditions for continuous learning.
- User-centric transformation, helping organizations rewire around experience and empathy.
- Leadership development, where the emphasis shifts from managing outputs to enabling curiosity, trust, and experimentation.
- AI-era adaptation, guiding leaders to balance technological acceleration with human-centered sensemaking.
In all of these, the underlying pattern is the same: we start in practice, not in theory.
The Role of the Practitioner-Teacher
As Jerry taught me, sustainable change is a craft. It requires presence, repetition, and humility — staying close to the teams as they transition from “trying something new” to “living it daily.”
One of the most fragile moments in this process is what I call the “Monday Morning Post-Workshop Blues.”
It’s the first normal workday after the magic of a high-energy sprint, conference, or pilot. The skilled practitioner has left the building, the adrenaline fades, and the whiteboards that yesterday looked alive with meaning now seem filled with cryptic fragments and half-remembered insights.
The team still believes in the potential, but lacks the immediate skill or confidence to translate that inspiration into action. The great beginning starts to feel like a hangover — a low-serotonin dip after the creative high. And it’s precisely here that most transformations falter.
Without guidance, teams either slide back into business as usual or overcompensate, rushing ahead without the deeper understanding that makes methods effective. Both outcomes are forms of reversion.
That’s why the practitioner-teacher must remain engaged during this fragile phase — helping the team decode what they created, transform fragments into frameworks, and anchor early excitement in capability. It’s in this delicate handover from inspiration to integration that real learning matures into knowledge — and the PAK cycle completes itself.
From Knowledge to Knowing
Ultimately, PAK is more than a model — it’s a mindset for how we learn, lead, and adapt. It honors the human truth that understanding follows experience. In a world defined by asymptotic change and accelerating technology, organizations can no longer afford to learn top-down and too late.
They must learn through doing, reflect through application, and codify through knowledge — in that order.
Are you preparing your organization for its next phase of transformation? Let’s explore how the PAK approach can bring your teams into faster alignment, deeper learning, and lasting cultural change.
Summary
PAK starts with practice and grows into shared knowledge.
KAP starts with knowledge and struggles to reach practice.
One is human, adaptive, and alive.
The other is academic, linear, and slow to change.
The choice between them defines not only how we learn — but how we lead.
hy is a tool worth considering. Let’s explore the possibilities together and usher in a new era of transformative success.
Leave a Reply