The most common pushback from organizations isn’t a question about whether the Place matters. It’s a question about whether they already have one.
The internal L&D team knows the audience. They built the programs. They own the content from design through delivery. They run the sessions, manage the calendar, and produce the dashboards. If any organization should already have a Place, the thinking goes, it’s the one with a fully resourced internal function doing exactly this work.
That case sounds strong. It has the wrong conclusion.
Ownership of delivery is not architecture. Those are two different things, and conflating them is how organizations end up measuring the wrong thing for years while the actual gap goes unaddressed.
What the L&D function is designed to do
An internal learning and development function is built around programs. It designs curriculum, runs cohorts, schedules sessions, and tracks participation. At its best, an internal L&D team understands the audience better than any outside vendor ever could. They know the culture, the resistance patterns, the language that works inside this organization and the language that doesn’t. That institutional knowledge is genuinely valuable. It is also specific to delivery.
The L&D function delivers. The Place holds what was delivered.
Those are different jobs. The first is organized around programs — discrete events with start and end dates, facilitation requirements, and completion records. The second is organized around the work itself — an environment where what was produced becomes findable, returnable, and usable after the program is over.
Most internal L&D functions have built the first one. Very few have built the second. This isn’t a failure of ambition or resources. It’s a function of what the L&D role is designed to optimize for. Programs have stakeholders, timelines, and deliverables. The environment that holds the work between programs has none of those natural forcing functions, so it rarely gets designed at all.
The dashboard problem
Internal L&D teams produce reporting. Attendance figures, completion rates, satisfaction scores, Net Promoter results from post-session surveys. Most of that data gets delivered to leadership in a format that looks like it is measuring something durable.
Internal dashboards look like Place metrics and measure something different.
Completion tells you that someone finished the module. Satisfaction scores tell you that people reported a positive experience. Attendance rates tell you the sessions ran. None of that tells you whether the work is being accessed between programs, whether the material is findable when someone needs a specific piece of it three months later, or whether anything that was produced has a real home that outlasts the cohort that went through it.
The metrics are not wrong. They measure what they measure. The problem is the category confusion they create. When leadership sees those numbers, the reasonable read is that the learning function is producing durable organizational value. What the numbers actually show is that programs are running and people are completing them. Those two things can both be true simultaneously: the programs work, and there is no Place for what they produced.
Organizations that have lived inside that confusion for a long time often resist the distinction. The dashboards feel like evidence of a Place because they represent ongoing activity, ongoing investment, and ongoing measurement. They are evidence of delivery.
The handoff problem
There is a pattern that almost every organization with a mature internal L&D function has experienced. An L&D leader builds something over three or four years. The programs are strong, the content has accumulated, and there are materials that took real effort to develop. Then that leader moves on.
The incoming leader arrives with their own philosophy, their own preferred vendors, their own sense of what the organization needs. The prior program gets assessed. Some of it gets carried forward, some gets archived, and the new leader begins building toward their own program cycle. The work the prior leader built doesn’t disappear exactly, but it stops compounding. It gets preserved rather than developed.
This is not a leadership problem. It is an architecture problem. What the outgoing L&D leader built was a program stack tied to their judgment and their relationships. What they didn’t build — and what the function doesn’t naturally create — is a layer underneath that survives the transition.
The Place operates underneath whoever runs L&D next quarter. A program stack doesn’t. It depends on continuity of leadership to maintain its coherence. When that continuity breaks, the work gets reset rather than extended.
Most organizations have experienced this cycle more than once. A new function leader comes in, inherits materials that don’t match their approach, and starts over. The organization keeps investing in delivery. The work keeps failing to compound.
What the Place is actually doing
The Place is the layer that organizes the work independent of who is running programs. It is where the material lives in a form that is findable — not archived, not stored in a folder, but arranged so that someone in the organization can access the specific piece they need at the moment they need it.
That distinction matters more than it initially sounds. An archive stores things. A folder stores things. Both are retrievable in theory and rarely retrieved in practice, because retrieval requires knowing what you’re looking for and where it lives. A Place organizes the work around how people actually return to it — by topic, by application, by the situation they’re in — rather than by program cycle or content category.
A speaker or expert builds a Place to give their body of work somewhere durable to live after each event. What a Place actually is — and what it requires — is a different question from what an L&D function is built to answer. An organization builds a Place for a different reason but arrives at the same gap: the programs are running, the material is being produced, and nothing is organizing it into an environment where it keeps working after delivery.
The training function doesn’t close that gap by running more programs. A more capable L&D team with better facilitators, stronger content, and higher completion rates still produces the same result at the architecture layer. The work gets delivered and stops there. A course platform has the same structural limit — it was built for delivery, not for the layer underneath.
Where Blueprinting fits
The question for any organization that has an internal L&D function isn’t whether to replace it. The function does real work that a Place doesn’t replace. Programs have to run. Facilitators have to show up. Cohorts have to move through curriculum.
The question is what happens to the work between programs, and whether anything is being built that outlasts any individual program cycle.
Blueprinting inside the Lab designs the Place that operates underneath whoever runs L&D next quarter. It is function-independent by design. The work it produces doesn’t depend on who is leading the L&D team this year or what program philosophy the current leader prefers. It creates the layer that holds the work between programs, makes it findable when someone needs it, and compounds over time rather than resetting when leadership changes.
That layer is not what the L&D function is built to produce. It is what makes the L&D function’s output last.
Frequently Asked Questions
Does an internal L&D team already have the Place if they manage a learning management system (LMS)?
An LMS is a delivery system. It routes learners through courses, tracks completion, and generates records. That is useful for compliance and credentialing — any situation where the organization needs to document that someone went through the material. What an LMS doesn’t do is organize the work for return. The architecture is sequential: learners move through the content once, the system marks them complete, and the experience is over. A Place is built on the opposite assumption — that the audience will need to come back to specific pieces at the moment those pieces become relevant, often long after the original program ran. Those are two different design problems, and most LMS platforms were built to solve only the first one.
If an organization invests in a Place, does that change what the L&D function does?
The L&D function keeps running programs. That work doesn’t change. What changes is what happens to the output. Instead of each program cycle producing materials that get archived when the next cycle begins, Blueprinting creates the layer where the work accumulates over time. The function delivers. The Place holds what was delivered. Both are necessary, and neither replaces the other. The distinction is that only one of them was built for the organizational environment most L&D functions have now — where leadership turns over, programs get redesigned, and the prior work keeps getting reset instead of compounded.
Why don’t more organizations build this layer?
The L&D function has natural forcing functions — stakeholders, timelines, completion targets — that create pressure to produce programs. The layer underneath, the environment that holds what was produced, has no equivalent forcing function. It doesn’t report to anyone in the way a program does. It doesn’t have a launch date or a completion rate. So it rarely gets designed. Organizations that recognize the gap often describe it as a content management or knowledge management problem and route it to the wrong function. Blueprinting treats it as an architecture problem, which is what it actually is.