The Executive Initiative®
The Institutions
of the Technical Revolution
Institutions fade into the background. We notice the inventions and forget the structures that made the inventions possible. Yet the structures are where the leverage lives. Each of the institutions below solved a problem of knowledge, how to access it, share it, accumulate it, or apply it, and each one prefigures a specific piece of the modern technology stack. The founders were not just building a country. They were building the operating system underneath it.
The earlier articles in this series have considered the founders as technologists, Philadelphia as the city where their technical revolution happened, and the journey that brought the founders there. This piece is about something less visible than the leaders, the city, or the journey. It is about the institutions they built, and about why those institutions should look familiar to anyone running technology today.
Five institutions make the case, all built in Philadelphia between 1727 and 1755, all with Franklin at or near the center. By the time the Continental Congress convened in 1774, they were already a generation old and simply part of the working equipment of the city. Each solved a different problem of knowledge, and each has a descendant in the stack you run today.
The Library Company
Access Without Ownership
In the 1720s, serious knowledge was gated by wealth. Books were expensive, a substantial library cost more than most tradesmen would earn in years, and so the people most likely to use knowledge were the least able to afford it.
In 1731, Benjamin Franklin proposed a fix that now sounds obvious and was then radical. Members would pool their money, the pooled fund would buy books no individual could afford, and every member could borrow from the shared collection. The Library Company of Philadelphia was the first subscription library in the colonies. It spread quickly, and by the Revolution it served as the de facto research library of the Continental Congress.
The mechanism is the part worth pausing on. The Library Company decoupled access from ownership. Before it, using a great library meant owning one. After it, you needed only modest dues and the will to study. Knowledge became something you could reach without having to possess.
That is the oldest idea in modern computing. It is the cloud. It is the move from buying the data center to subscribing to the capacity, from owning the software to renting access through an API, from the private archive to the shared repository. Every executive who has shifted capital expense to operating expense, who has chosen access over ownership because access compounds faster, is working a principle the Library Company proved in 1731. The internet itself is the Library Company at planetary scale, the pooled collection no one owns and everyone can reach.
The Junto
The Structured Peer Network
Four years before the Library Company, Franklin built something smaller and arguably more influential. In 1727, at twenty-one, he founded a discussion club he called the Junto.
It is easy to mistake the Junto for a social club, and easy to miss why it worked. The membership was capped. It met on a fixed cadence. It ran on an agenda, with questions proposed in advance and discussed at the next session. Members were expected to read, to prepare, and to build on the previous conversation rather than start fresh each week. It was, in modern terms, a working group with governance and a backlog.
The output was extraordinary for so small a group. The Junto seeded most of the other Philadelphia institutions that mattered, including the Library Company itself. A handful of disciplined people, meeting regularly under structure, compounded their thinking into a civic infrastructure.
This is the model behind every serious peer network operating today, the executive roundtable, the community of practice, the standards working group, the small board that meets under structure precisely because structure is what turns conversation into output. The technology leaders who get the most from their peers are not the ones who network the widest. They are the ones who commit to a small group, a real cadence, and the discipline of doing the homework.
The Junto is the proof that the highest-leverage room is often the smallest one, run well.
The American Philosophical Society
Interoperable Knowledge
By the 1740s, Philadelphia had outgrown informal exchange. There was enough scientific activity that the loose circulation of letters and conversation could no longer keep up. In 1743, Franklin, with John Bartram and others, founded the American Philosophical Society to promote, in the phrase of the day, useful knowledge.
The Society did what we would now recognize as peer review and a conference circuit in a single institution. It met regularly, corresponded with counterpart bodies in Europe, published proceedings, and maintained a shared collection of instruments. But its most forward-looking feature was who it let in. Mathematicians sat with physicians. Astronomers sat with botanists. Tradesmen with practical expertise sat with the formally educated. The Society was built on the premise that useful knowledge crosses boundaries, so the institution had to cross them too.
That premise is the one modern technology organizations relearn constantly and at cost. Value rarely sits inside a single discipline. It shows up in the seams, when the data scientist talks to the operator, when security sits with product, when the people who hold practical knowledge are in the room with the people who hold formal authority. The Society is the ancestor of the standards body, the open research consortium, and the cross-functional team, all of which exist to make knowledge interoperable across silos that would otherwise hoard it. Its lesson is that the boundaries an institution refuses to enforce are often the source of its advantage.
The Pennsylvania Hospital
The Learning System
A hospital can look out of place on a list about technology. In 1751 it was not, because the Pennsylvania Hospital, founded by Franklin and Dr. Thomas Bond as the first true hospital in the colonies, was designed to do something almshouses and pesthouses did not. It was built to learn.
The distinction is the whole point. Earlier institutions for the sick provided shelter. The Pennsylvania Hospital provided care, but it also kept records, trained the next generation of physicians from the College of Philadelphia’s medical school, and corresponded with European hospitals about what worked and what did not. Treating a patient produced knowledge, the knowledge improved the treatment, and the improvement was captured rather than lost. Benjamin Rush practiced there for much of his career.
That loop, run the operation, capture what the operation reveals, feed it back to improve the operation, is the defining ambition of the modern instrumented enterprise. It is telemetry. It is the analytics practice that turns operational exhaust into institutional memory. It is the difference between a system that merely runs and a system that gets better the more it runs. The Pennsylvania Hospital understood in 1751 what many organizations still struggle to operationalize in 2026, that the most valuable byproduct of doing the work is the data about how the work went, and that an institution which fails to capture it is leaving its compounding advantage on the floor.
The College of Philadelphia
Teaching What Is Useful
Most colleges in colonial America trained clergy in the classics. Franklin wanted something different, and in 1755 the College of Philadelphia, today part of the University of Pennsylvania, became the first American institution of higher learning to put practical and scientific knowledge in the curriculum alongside the classics. It founded the first medical school in the colonies in 1765, and its early graduates included signers of the Declaration, physicians, scientists, and political leaders.
The founding philosophy is captured in a phrase from Franklin’s proposal that reads as though it were written for a modern capability strategy. Students should learn, he wrote, “those Things that are likely to be most useful.” Almost casually, he reoriented education away from inherited prestige and toward applied value.
Every technology organization now lives that tension. The credential is not the capability. The half-life of a specific skill keeps shrinking, and the institutions that thrive are the ones that build the capacity to teach what is useful now, the internal academy, the reskilling function, the deliberate investment in growing talent rather than only buying it. Franklin’s line is a remarkably current statement of how a serious organization should think about its people, that the test of what to teach is not what is prestigious but what is likely to be most useful.
The Pattern Underneath
Step back from the five and the pattern is hard to miss. Each institution solved a knowledge problem, and each was built the same way.
Each was designed, not stumbled into. Franklin and his colleagues named a problem and built a structure to solve it, with bylaws, a cadence, and an explicit purpose. Each was built to compound, so that the work of one year made the next year more productive, books accumulating, proceedings accumulating, case records accumulating, graduates accumulating. Each was deliberately open in ways its era found unusual, because the founders understood that gatekeeping along conventional lines was a tax on the very knowledge the institution existed to grow. And each was built to outlast the people who built it. Franklin died in 1790. The Library Company still circulates books, the Philosophical Society still publishes, Penn still teaches, the Pennsylvania Hospital still treats patients.
The founders built for a horizon they would not live to see, which is among the hardest disciplines of leadership in uncertain times.
What This Means for the Technology Executive
The reason all of this should feel familiar is that the modern technology executive is, whether the job description says so or not, an institution builder.
The data architecture is an institution. The governance model is an institution. The community of practice, the analytics function, the internal academy, the peer network the executive chooses to join, all institutions. The functioning enterprise is not a pile of systems. It is a stack of institutions resting on one another, and the systems are only as durable as the institutions around them. A platform with no governance decays. A tool with no practice around it goes unused. A capability with no way to teach it leaves when its expert leaves.
This is what the founders understood, and it is why their institutions are still running three centuries later. They were not only building the technology. They were building the structures that let knowledge accumulate, access widen, disciplines connect, operations learn, and people grow. Those structures were the real invention. The institutions are the technology behind the technology, and that was as true in 1731 as it is in the architecture review you will sit through next week.
A Closing Thought
The next time you walk past Philosophical Hall on Independence Square, or the original building of the Library Company, or the Pennsylvania Hospital on Eighth and Pine, do not see them as historical buildings. See them as running systems, the working artifacts of a generation that thought carefully about how knowledge should be accumulated, shared, and applied, and that built structures durable enough to still be doing it. The institutions, properly designed, simply keep working.
The founders’ instinct was always to build the system and not just the part. The Constitution was the largest institution they designed, and they designed it the way they designed everything else. That habit, the reflex to build systems rather than isolated components, is the subject of the final article in this series.
Join Us
in Philadelphia
The CIO Initiative® Summit Philadelphia takes place September 23 and 24, 2026, a few blocks from Independence Hall, Philosophical Hall, and Rittenhouse Square. If you are a C-level technology executive and would like to be part of the conversation, you are invited to register.