Field Notes · By Stephen Gilfus · November 3, 2000
Building Blocks (B²) — The Architecture That Made Blackboard a Platform
Revisiting the November 3, 2000 whitepaper with Matthew Pittinsky.
On November 3, 2000, Matthew Pittinsky and I introduced the Building Blocks (B²) Initiative — system services, supported interfaces, and a partner-extensible toolset that turned Blackboard into the academic e-Learning operating system.
Blackboard Building Blocks (B²) Initiative, co-authored with Matthew Pittinsky on November 3, 2000, is the companion paper to the December 2000 product strategy — and arguably the more architecturally consequential of the two.
The B² initiative made one decision and built an architecture around it: Blackboard would not try to build every learning tool itself. Instead, it would expose a defined surface — system services, supported interfaces, an extensibility toolset — and let an ecosystem of partners build on top.
Three structural commitments came out of that decision:
System services as the contract. Authentication, course context, gradebook, content, communication — these were defined as platform-level services with stable interfaces, so partners could build against them with confidence.
Supported interfaces as the boundary. Rather than expose every internal API and trap the platform in backward-compatibility forever, B² defined a curated set of supported interfaces. The boundary was explicit.
The partner-extensible toolset as the value. Tools, building blocks, and integrations from partners became part of the platform's value proposition — not just a feature list, but a network effect.
Every modern LMS plug-in marketplace — and arguably every modern SaaS app marketplace in any vertical — is descended from this architectural pattern. Worth re-reading any time you're scoping the API and extensibility surface of a platform you're trying to build.
Share