Helping organizations turn knowledge into practical capability

Knowledge is one of the most valuable strategic assets of every organization. Yet most organizations rarely struggle because they lack knowledge.

The gap between knowledge and actual work

In many organizations, knowledge exists somewhere – in documents, systems, trainings, or people’s heads.
The problem starts when it is disconnected from daily work.

Learning without context

Content exists, but it’s disconnected from real tasks, tools, and decisions people face every day.

Systems people work around

Platforms and systems are technically sound, but don’t fit how work actually happens – so teams bypass them.

Onboarding that doesn’t carry over

New hires complete onboarding, but still rely on informal knowledge and ad-hoc support that costs your experts precious time.

Ownership that never really forms

Once external support steps back, learning slows down. No one feels responsible for keeping it alive – or knows how to.

SYSTEM IMPACT

These are not people problems. They’re system problems.

When knowledge is disconnected from daily work, the effects show up across the organization – often quietly at first, but with real operational consequences.

Slower ramp-up

New employees need more time to become confident and productive because critical knowledge is not available in a clear, usable structure.

Repeated clarification loops

Experts, managers or HR teams are asked the same questions again and again because knowledge is not easy to find, trust or apply.

Inconsistent execution

Teams rely on different sources, habits or local explanations, which can lead to variation across roles, shifts or locations.

Unclear responsibility

Knowledge exists, but ownership for keeping it current, usable and connected to real work is not clearly defined.

This is where knowledge, learning and enablement need to be designed as a system – not as isolated initiatives.

What this means in practice

Enablement means making sure people can do their work effectively – because they understand what is expected, how things work, and where to find the knowledge they need. That requires more than training. It means structuring knowledge, onboarding, learning formats and systems so they support daily work and can be maintained over time.

Where organizations typically involve me

Most projects start with a specific challenge. What looks like an onboarding, training, or documentation issue often turns out to be a broader knowledge and enablement challenge.

Knowledge

Know-how often exists already – with the people doing the work, or spread across documents – but isn’t yet easy to find, trust, or pass on. I help bring structure to it, and shape the strategy for getting it to where it’s needed.

Learning

Once the knowledge exists, it needs to reach people in a form that fits how they actually work. I build the training, platforms, and materials for that – for example videos, interactive modules, or knowledge units to use in AI tools – shaped around real constraints, like compliance, limited device access or little time between tasks.

Impact

Once knowledge is structured and reaches people, the work continues: tracking whether it’s actually used, gathering feedback, and identifying what needs to change. What we learn here flows back into Knowledge and Learning, keeping the loop going rather than treating rollout as the finish line.

Enablement Team

Behind Knowledge, Learning, and Impact, there’s usually a team meant to run them day to day – across whatever systems carry the work, for example an LMS, a knowledge hub, or internal documentation. I help build that team where it doesn’t exist yet, or strengthen it where it’s stretched too thin, so the work keeps running without me.

How we work together

The work is structured, collaborative, and grounded in real constraints – not slide decks or abstract models.

1. Understand the current state

We start by clarifying how knowledge, learning and work actually happen today – through focused analysis and direct collaboration.

2. Define what needs to change

Together, we identify priorities, constraints and a realistic target state – separating what matters now from what can wait.

3. Build, test, improve and hand over

We implement the agreed changes together, test them against real work, refine based on what we learn, and hand over clear ownership so your team can keep evolving the system without permanent external support.

Who this is for

This work is for organizations where knowledge, learning and enablement are tied to real operational outcomes – not just internal programs.

Organizations with real operational complexity

Manufacturing, production, regulated environments, or fast-growing organizations where mistakes have real consequences – and learning needs to work under pressure.

Teams responsible for capability, knowledge, or operations

Such as HR, L&D, Operations, Safety, or Enablement – who need structures that hold up in daily work, not another initiative that fades after rollout.

Leaders who value ownership over dependency

Leaders who want to build internal capability instead of outsourcing responsibility – and are willing to work collaboratively to get there.

Who is behind this?

Hi, I'm Katrin.

Throughout my career, the roles, industries and responsibilities changed – but one question stayed the same:

How can people do good work without fighting the way knowledge is shared, structured or maintained?

That question became HOK Enablement. It’s the work of reducing the gap between what an organization knows and how that knowledge is actually used in daily work.

Frequently Asked Questions

What exactly is HOK Enablement?

HOK helps organizations turn knowledge into practical capability. I work where knowledge needs to be found, structured, shared and used in daily work – so people can do their jobs better and the organization becomes less dependent on individual people.

What usually brings organizations to HOK?

HOK is for organizations that want to make better use of what they already know. That can involve HR, Learning & Development, Operations, IT, executives or internal knowledge owners – the starting point matters less than the need to make knowledge usable. Most conversations start with something concrete: an LMS, onboarding, scattered documentation, expert knowledge, AI, low adoption or knowledge that lives in too few heads. Those are valid starting points. From there, we look at what the organization is actually trying to achieve.

How do you decide what the right solution is?

I start by understanding the goal, the current situation and the constraints. Then I look at what knowledge is needed, who needs it and where it needs to work in daily practice. The right solution is the one that fits the organization – not the one that sounds best in theory.

Do we need to know exactly what we want before we talk?

No. Many projects start with a symptom, an idea or a rough direction. You do not need a finished brief. The first step is to understand what is happening, what you want to improve and whether HOK is the right fit to help.

Do you only advise, or do you also help with implementation?

Both. I can support strategy, structure, content, systems, rollout and internal enablement. The exact scope depends on what is needed – from a focused review or workshop to hands-on implementation and team training.

What happens in a first conversation?

We look at where you are right now, what made you reach out and what outcome would actually matter. It is not a pitch call. The goal is to understand whether there is a useful next step. If it makes sense, the next step can be a focused workshop or assessment.

Can we keep the systems we already have?

Usually, yes. I start with what already exists. If your current systems support the goal, there may be no reason to replace them. If another setup would work better, I will explain why.

What happens after the project ends?

The goal is not permanent dependency. HOK projects are built to leave behind clearer structures, stronger ownership and teams that can continue the work themselves.

Contact

Ready to explore what’s possible?

Conversations start in different ways – with a clearly defined project, a concrete problem, or open questions about what needs to change. All of these are welcome.