Who’s Afraid of Bottom-Up? Making Knowledge in SMEs Scalable

Portrait Jonas Basten

From

Jonas Basten

Posted on

5.11.2025

Many companies face the same challenge: knowledge exists in abundance, yet it’s rarely accessible or actionable. What’s often missing is the willingness to build and maintain knowledge collaboratively with employees. But for many organizations, the term bottom-up still sounds like chaos, loss of control, or extra effort. In reality, it has never been more important — especially for small and medium-sized enterprises — to absorb, share, and preserve their know-how.

And the best place for that? A management system that works like a sponge. Here’s what we mean:

Usefulness or just paperwork?

For years, many companies have rolled out their processes top-down — often driven by certification requirements, with templates, handbooks, and folders. But today, it’s not about collecting certificates; it’s about creating impact and practical value.

If a management system continues to be run centrally, the outcome is predictable: usage declines, content becomes outdated, and value fades.

That’s where the sponge comes in.

Participation creates structure

You’ve probably guessed it: the sponge is just a metaphor. It stands for a management system that absorbs knowledge where it’s created — by the people doing the work.

As employees document their processes and improvement ideas directly within an interactive management system, their expertise becomes visible and accessible to everyone.

Just like a sponge, the system soaks up knowledge throughout the organization — and can be “wrung out” whenever it’s needed. Roles, approvals, and version control ensure that this doesn’t turn into chaos.

Bottom-up doesn’t mean disorder. On the contrary: participation creates structure.

But where do you start?

Your 3-step plan for bottom-up knowledge

The key is to start pragmatically: begin small, document in the flow of work, define responsibilities clearly, and make early successes visible. Once the effort-benefit ratio flips, momentum follows quickly.

Here’s a practical roadmap:

Step 1: Define your vision and foundation

  • Define a target vision, scope, and 2–3 key metrics (e.g., onboarding time, search effort, update rate).
  • Assign one responsible person per process and a backup.
  • Create lean templates for processes and work instructions, ideally in tabular form.
  • Set rules for naming, versioning, and reviews. Establish a central repository — in a new tool or your existing IT landscape.

Step 2: Pilot and scale

  • Introduce a clear change workflow with full traceability from idea to approval.
  • Launch a pilot area, train responsible users, and gradually expand to other teams.
  • Link to your new structure wherever people actually work — in the intranet, file storage, or specialist systems — so content is easy to find.
  • Collect feedback systematically and refine templates as needed.

Step 3: Stabilize and measure impact

  • Continuously expand content across all areas. Assign final process owners and backups in your documentation.
  • Set up review reminders, monitor update rates, and archive outdated information cleanly.
  • Communicate success openly — through KPI reports or quick wins.
  • Fine-tune your governance, assess effectiveness, and plan the next rollout steps.

Using knowledge without losing control

SMEs thrive on knowledge, experience, and collaboration. An interactive management system helps make that knowledge visible, preserve it, and continuously evolve it — without losing control.

Bottom-up isn’t a risk. It’s your opportunity to make your organization’s knowledge transparent, scalable, and truly useful. Seize it.

No items found.

Your question to Carsten

Sign in to get in touch with Carsten directly.

Don't miss any more new posts!

Always stay up to date: In our newsletter, we provide you with a fresh update on the Modell Aachen Insights every month.

Desktop and mobile illustration

Similar posts

See all posts