A structured knowledge management workspace built for long-term internal ownership — serving multiple departments, supporting guest contributors, and maintained independently from day one.
Günther Business Solutions is a software engineering company with a clear operational challenge: years of distributed documentation, no shared knowledge infrastructure, and growing pressure to get internal processes, guidelines, and expertise out of people's heads and into a system teams could actually use.
The goal was to build a structured knowledge management workspace in Notion — one that could serve multiple departments with different documentation needs, support both full team members and guest contributors, and be maintained and extended by internal owners without ongoing external dependency.
The project unfolded over six months across a series of structured working sessions — each one combining progress review, live configuration, and direct knowledge transfer to the internal team.
Rather than delivering a finished system at the end, the workspace was built incrementally and in close collaboration with the internal champions. Every architectural decision — from the document database structure to how teamspaces were organized, how permissions were modeled, and how guests would navigate the system — was developed through dialogue. The internal owners shaped the design as it was built, which meant they understood it deeply enough to extend it themselves.
Sessions alternated between consulting-led design work and hands-on workshops with the team: reviewing what had been built, testing it against real content, and adjusting based on what actually worked in practice. Training wasn't saved for the end — it was woven throughout. By the time the system was ready to roll out, the internal champions weren't just familiar with it — they were equipped to onboard colleagues, manage permissions, and keep the workspace evolving independently.
A structured document management system with a three-tier category hierarchy (~100 categories), a central document database, and department-specific views. Documents are created via form-based entry to ensure correct classification and prevent orphaned content. An inbox workflow catches unassigned documents before they get lost.
Department-specific teamspaces — including Marketing, Office, and core functional areas — each with their own dashboards, navigation, and locally relevant views, connected to the central document infrastructure. A color-coding and icon system provides consistent visual orientation across the workspace.
A carefully designed permissions architecture distinguishing between full team members and guest contributors. Guests can add and edit content within defined boundaries without being able to alter the workspace structure — enabling external collaboration without governance risk. A central welcome and navigation page provides a clean, guided entry point for guest users.
A reusable template library covering the main document and content types across departments — including marketing assets, internal documentation, and blog/newsletter formats — providing structure without rigidity.
Video walkthroughs from the guest perspective, step-by-step permission management tutorials, and a structured training concept for internal rollout — ensuring the team had everything needed to onboard new users independently.