Most planning failures happen in the four weeks before registration opens, not on the day of the event. Here's the checklist we use across our member network.
Begin writing the next section…
LibraryArticles New article
Draft About
We built expertshare because expertise deserves better than a feed.
Professional expertise — the kind people spend whole careers building — deserves a permanent, structured home. Not a feed that forgets it. Not a tool that buries it. A world that keeps it alive. That single belief is the design constraint behind every decision we have made, and the foundation of the Living Knowledge Platform we built: knowledge infrastructure that makes professional knowledge compound instead of disappear.
Why this platform exists
We kept watching good knowledge die in the wrong tools.
Across organizations and institutions, the same pattern kept repeating: decades of hard-won expertise, forced through tools that were never built to hold it — and quietly lost as a result.
Presentations emailed around as PDFs and never seen again. Training programs running on an LMS no one wanted to open. Events that ended leaving no trace behind. The knowledge was real and valuable. The infrastructure underneath it was not. Every organization was rebuilding the same broken stack, and every one of them was losing the same knowledge the same way.
So we made a deliberate early decision: build the infrastructure first, not a product bolted to one workflow or one sector. A knowledge platform capable of holding professional knowledge in every form, at any organizational scale, connected across the industries where that knowledge actually matters. Starting with healthcare was a choice, not an accident — it is one of the most demanding environments for professional knowledge there is: complex compliance, continuing education requirements, and lives depending on accurate information. It does. Insel Spital, the University of Bern, RUAG, and Credit Suisse all run their own spaces in the same cluster today — so a clinician, a researcher, and an enterprise team operate inside one connected field instead of four disconnected tools.
doclift is the healthcare vertical built on expertshare — the first complete industry in the ecosystem. doclift is the proof of method, not the brand. The exact architecture that powers doclift is the architecture now being prepared for pharma, finance, education, and professional associations. doclift demonstrates the model. Every next vertical inherits it intact.
If the model holds in healthcare, it holds anywhere. It does.
What we believe
Five convictions that shape every decision we make.
Not a values page. These are the constraints we design against — each one ruling out an easier product we chose not to build.
-
Knowledge in isolation depreciates.
Knowledge trapped inside one organization dies with it. The moment it enters a connected ecosystem — structured, linked, discoverable — it becomes something far more durable. Knowledge in infrastructure is knowledge that compounds.
-
Organizations own their space completely.
The platform provides the knowledge infrastructure and makes no claim on what lives inside it. Ownership and independence are not premium tiers you upgrade into — they are the architecture itself.
-
Learning is continuous, not episodic.
A single course or event is one moment in a long professional journey, and that journey should accumulate, not restart at every platform boundary. Episodes end. Expertise, given the right home, compounds.
-
Identity has to be permanent.
Professionals should carry their credentials and continuing education everywhere they go, not rebuild their record every time the tool changes. A career is one continuous thing — even when the tools that hosted pieces of it disappear.
-
Industries deserve their own worlds.
Built correctly from the inside out — not scaled fast and patched later. In knowledge infrastructure, depth beats breadth every time. One industry built properly is worth more than five rushed to market.
Proof of method
doclift is what one industry looks like when it is built correctly.
doclift is the ecosystem's first complete vertical: hospitals, medical associations, universities, and clinical specialists, each running their own independent space, all connected through one industry. Insel Spital, the University of Bern, RUAG, and Credit Suisse run their spaces in the same cluster — so their people work, learn, and share inside one professional ecosystem instead of stitching together separate intranets, learning systems, and event tools. Healthcare is the proving ground, chosen precisely because it is unforgiving.
What doclift proves is simple: depth-first works. One industry, fully built — with governance, identity, discovery, and content formats that actually match how healthcare professionals learn and share knowledge. Not five thin verticals racing for market share, but one industry functioning at the level the architecture always promised. That is the difference between a demo and a knowledge platform.
doclift is what we built first. It is not what we are. The same architecture is being prepared for pharma, finance, education, and professional associations, and each next vertical inherits doclift's depth, its governance model, its identity layer, its discovery mechanics — fully formed, on day one. The pattern replicates. The brand does not have to.
Proof, not promise
The model already runs in production.
The first vertical is live: an anchor hospital, a leading university, and regulated enterprises all running their own spaces in one connected cluster.
-
Insel Spital
The anchor of the first vertical
The founding hospital runs its own space in the cluster — so clinicians work in one connected field instead of stitching together separate intranets and event tools.
-
University of Bern
Academic knowledge that lasts
Continuing education and post-graduate programs run on the same infrastructure, where researchers and alumni stay engaged for years.
-
RUAG · Credit Suisse
Proven where it is hardest
Regulated, security-conscious enterprises run their own spaces in the same cluster — evidence the model holds in the most demanding environments.
How an article actually moves through the platform.
From a draft a contributor types in their browser to a result that surfaces when someone searches months later. Same article, four states.
LibraryArticles Annual conferences
In review How to run an effective annual conference
Most planning failures happen in the four weeks before registration opens, not on the day of the event. Here's the checklist we use across our member network.
LibraryArticles Annual conferences
Live How to run an effective annual conference
Most planning failures happen in the four weeks before registration opens, not on the day of the event. Here's the checklist we use across our member network.
Start with venue lead time. Conference-grade venues book 9–14 months out, and the better ones won't hold a date without a deposit. Lock this before everything else.
Bookmark Share 128 reads · 14 bookmarks
Library Search
Search How to run an effective annual conference
Most planning failures happen in the four weeks before registration opens, not on the day of the event…
Venue contracts: what to negotiate first
Most planners hand the negotiation to procurement. Don't. The clauses that bite are operational, not commercial…
Run-of-show templates for board-level events
Four templates, each tested on at least one 400-person event. Includes contingency time and break logic…
autoplay step 1 of 4 · hover anywhere to pause
Running their own spaces in the same cluster
- Insel Spital
- University of Bern
- RUAG
- Credit Suisse
Logos shown as placeholders — brand approvals confirmed on our first call.
Understand the world — or start building in it.
Two genuinely different next steps. Neither one is a push.