We helped B. Amsterdam turn scattered knowledge into one shared source of truth.
The result?
- One central knowledge base
- Less dependency on individual people
- Clear, department-specific workflows
Intro
B. Amsterdam is a shared office environment in Amsterdam, comparable to Spaces or WeWork, renting out office space and running the day-to-day facilities across three buildings. As the community and team have grown, so has the amount of daily coordination, events and cross-team activity. Maaike Visser's role is shifting alongside that growth: from leasing, events and community towards building the processes and structure the organization needs, while also keeping the community connected. That shift is exactly why B. Amsterdam brought in Notion.
The challenge
As B. Amsterdam grew into three buildings, several departments and an expanding community, knowledge and processes became increasingly scattered.
- No central place existed for company knowledge or a handbook
- Information lived mostly in individual people's heads
- Recurring tasks and workflows were rarely written down
- Day-to-day work depended on informal handover between colleagues
- Consistency across the three buildings was hard to maintain
This made it harder to keep departments aligned and to pass on knowledge as the team kept growing.
What we build
Central Knowledge Base
We're building one central hub in Notion for B. Amsterdam's workflows, handbook and recurring processes, so knowledge no longer depends on one person.
Department-by-Department Discovery
Together with each department, we're mapping out where the biggest bottlenecks and most repetitive tasks sit, so the right processes get documented first.
Practical Workflows
For Marketing, for example, we're structuring how content input gets collected — what needs to be posted, which visuals belong to it and when it should go live — turning a scattered process into one clear workflow.
One Shared Structure
We're setting up a central B. Amsterdam hub with company-wide information such as team members, remote days, one-on-ones and brand guidelines, branching into dedicated spaces for Marketing, Facility, Events and Core.
Replace with Mockup
The result
B. Amsterdam is still early in this journey, but the direction is already clear. Instead of knowledge sitting with one person, the team is building a system where information, workflows and processes are documented, shared and easy to find.
- One central knowledge base instead of scattered information
- Less dependency on individual people
- Clear, department-specific workflows
- A foundation the whole team can use, not just Maaike
The changemaker
Foto van Maaike?
Now everyone can find what they need in one place — we're no longer dependent on one person having all the knowledge.
Maaike Visser, B. Amsterdam
