From the Written Word to Web Databases: The Technology Pattern behind Digital Transformation

As always I try to understand what drives success and failure in systems within organisations in the hope that it may allow me to understand where, when and how I should make effort to really make a difference in driving development. I wanted to take a step back and look more widely at transformation and see if there was a pattern that might be generally applicable and which I might be missing or I might be underappreciating and could form the strategic basis in moving processes forward in any situation.

The journey from ancient record-keeping to modern cloud architectures follows a pattern that after consideration looks to approximate technology trees in video games.

Civilisations don’t wake up one day and say, “Let’s invent databases.” They solve immediate problems using the tools available at the time, and each solution quietly unlocks the pre-requisites for the next. Over time, these incremental steps form a path that can still be seen in processes and organisations today. Below I lay out that path right from medieval times (although there is a before step that involves the language creation and then literature and universal education). It has important implications for process implementation within organisations today. Particularly 2 points
1) Not all sections within an organisation may be at the same stage
2) You cannot skip a tier you need to complete that tier before moving on to the next level.

Importantly you can almost guarantee that if a section or organisation is at a level they will be experiencing very predictable and similar problems. It is also why when you are in a meeting discussing transformation one section can be very pleased about a suggestion and another extremely worried. One may be ready for the next step while the other isn’t.

So the journey I lay out here is from the written word to web accessible databases but lets break it down.

🪵 Tier 1: Physical Records — The Dawn of Organisational Memory – Clay Tablets of Mesopotamia

Value:

  • Information persistence
  • Standardised transactions
  • The first administrative systems

    Features:

  • Clay or wooden tablets — ledger entries, grain tallies, tax receipts
  • Papyrus, parchment, early paper — lighter, portable, more space-efficient
  • Bound volumes and filing cabinets — organisation at scale
  • This tier is about capturing information. Most early organisations — temples, city-states, guilds — stored what mattered where it physically happened. It is also clear that generalised education that teaches reading and writing is a pre-requisite.

    But physical media has predictable constraints:

  • Hard to duplicate
  • Easy to lose
  • Slow to search
  • Geographically fixed
  • These constraints create pressure for the next unlock.

    📄 Tier 2: Industrial Paper Systems — Bureaucracy as Technology

    Value:

  • Large-scale administration
  • Mass literacy in record-keeping
  • Distributed offices
  • The start of standardisation of processes allows optimisation of process and users to learn procedures.

    Features:

  • Carbon copies
  • Central registries
  • Off-site storage
  • Standardised forms
  • Once institutions scaled (banks, insurance, public authorities), paper became its own ecosystem. Entire professions grew around organising it.

    But again, friction accumulates:

  • Duplication becomes expensive
  • Audit trails get messy
  • Collaboration is slow
  • Throughput bottlenecks emerge
  • The solution wasn’t digitisation yet — it was mechanisation: punch cards, microfilm, early typewriting pools. These were transitional “minor techs” that set the stage for the next leap.

    💾 Tier 3: Digital Files — Information Without Geography

    Value:

  • Immortality of Data
  • Speed
  • Duplication
  • Storage
  • Basic automation
  • Transfer of data at effectively zero cost

    Features:

  • Word documents
  • Spreadsheets
  • Local drives
  • Network folders
  • Email attachments
  • This tier feels modern because it still dominates everyday work. But digital files mainly replicate paper’s logic:

    It still involves

  • Individual documents
  • Manual version control
  • Human-based workflows
  • Shared drives acting like filing cabinets
  • It’s the same mental model — just running faster.

    Still, once organisations reach a certain size, digital files reveal their limits:

  • Who has the latest version?
  • Where do we store the truth?
  • Why is this data locked in 400 spreadsheets?
  • In particular often these files are only accessible by one person at one time.
    Additionally finding information is incredibly difficult.

    These questions unlock the next tier.

    🗄️ Tier 4: Databases — Structured Truth

    Value:

  • Querying
  • Consistency
  • Multi-user access
  • Transactional integrity
  • Unlimited access to a single source of truth by essentially a limited no of actors – (usually those on the same network with the same installed software).

    Features:

  • Relational databases
  • Normalised schemas
  • Application logic
  • ETL pipelines
  • Enterprise data warehouses
  • The database tier represents the moment information stops being “documents” and becomes structured knowledge.

    Instead of stacks of files, you get:

  • Tables
  • Relations
  • Indexing
  • Constraints
  • Automated integrity rules
  • Once you hit this level, the organisation’s memory becomes machine-readable instead of human-readable. In certain circumstances the distribution of these systems can be quite wide but usually limited to a local area network.

    And that unlocks the next big thing.

    🌐 Tier 5: Databases With Web Access — Web Accessible Structured Truth

    Value:

  • Internet available reach
  • Real-time collaboration
  • APIs as connective tissue
  • Dashboards and analytics
  • Workflow automation
  • Often the database structure and information need not change and importantly the Web UI can either replace or be in addition to the existing UI.

    Features:

  • Web front-ends
  • Cloud(Server) hosting
  • REST APIs
  • Identity & access management
  • Cross-department systems
  • This is where most modern digital transformation efforts sit:
    Moving from “a database in a room” to “a platform accessible across the web”

    This tier interestingly is in principle similar to Tier 4 i.e networking of a database. Interestigly by using the web as an interface the world standardised on a client opening the way forward for client portals and allowing for unlimited scaling of access to the databases. As such web uis offers true worldwide access to databases on mobile and desktop devices allowing organisations, their customers and their employees to be coordinated from anywhere in the world from nearly all devices and allowing systems and numbers to scale almost infinitely for very little cost.

  • Teams collaborate in real time
  • Processes become measurable
  • Systems integrate across old boundaries
  • Organisational intelligence compounds
  • No requirement for local installation is a big big thing
  • It’s the first point where the system becomes alive.

    🌱 This Technology Pattern is Emergent and people instinctually see parts of it. There are armies of individuals who have tried to take paper sheets and create excel spreadsheets employees will do this without being told because the value is evident.

    The important points are

    You CANNOT skip a Tier
    You can’t go from papyrus to APIs without unlocking the intermediate technology (literacy, filing systems, computing, data modelling).

    And once a tier is unlocked that tier must be maintained, organisations feel the tension that pushes them toward the next:

  • Paper creates filing problems
  • Digital files create versioning problems
  • Databases create accessibility problems
  • Web databases create integration problems
  • Integration creates analysis problems
  • Every stage solves the previous stage’s bottleneck while generating new ones that only future tiers can handle.

    That’s why digital transformation often feels both chaotic and inevitable.
    It’s not just technology — it’s organisational evolution.

    🧠 The Hidden Lesson
    If you understand your organisation’s place on this tech tree, you can predict:

    What problems you’re supposed to be having?
    What capabilities you’re ready to unlock?
    What investments will compound rather than stall?
    Digital transformation works best when you recognise it as the next natural step in a centuries-long lineage of humans trying to remember things better.

    We’re still following the same path the Sumerians started — we’re just moving much faster and there might be a lifetime of work moving from digital files to web UI databases.

    Practical Example
    So at the weekend I converted a largely single database file which was arguably Tier 3/4 to an web accessible tool. Significant improvements to the operation of the application for timing a race.

    Web Accessible Database Centric Workflows – A simple target for True Digital Transformation (Succession Resilient)

    Many organisations continue to go through a process of digital transformation – but can we more clearly define the principle measure of success for this strategy — Too often for many organisations the process stalls at the “file-based” stage. Spreadsheets, shapefiles, and local data silos persist after the move to cloud-based systems has taken place because although the platform on which data is stored is now a cloud server the continual use of file based storage continues to limit distribution of information. This is because real transformation comes not from the cloud itself, but from structured, version-controlled, and web-accessible enterprise databases.

    Overall Strategy : Move from Network Accessible Digital Single Files to Web Accessible Enterprise Grade Database Workflows. At the heart of a reliable digital infrastructure lies databases. Unlike flat files, relational databases ensure data integrity through enterprise grade security and version control. This improves the following.

  • Minimises potential file curruption from multiple users editing the same dataset at the same time.
  • Improves ability to search through large datasets.
  • Complete traceability of every transaction.
  • Recovery after failure or interruption.
  • True concurrency and reliability for multi-user environments improving version control truly solving reconciliation issues.
  • For spatial data, PostGIS extends PostgreSQL to store and query geometry objects natively — perfect for organisations managing maps, assets, or infrastructure data.
  • Web-Enabled Editable Databases accessible through Browser-Based Interfaces. Once data is stored in relational databases, the next step is to make them accessible to users through secure, web-based interfaces. This can be done using a wide range of established and well-supported technologies and organisations have the option of running these in parallel.

    These interfaces allow staff to edit records, maintain registers, update project systems, and manage operational datasets directly using familiar web forms and tables, rather than passing around emailed spreadsheets or local files.

    The essential point is that the database remains authoritative, while the web interface provides controlled, permission-based access.

    This approach brings multiple organisational benefits:

  • Data is always current, and everyone sees the same version.
  • Editing workflows can be controlled with user roles and permissions.
  • Versioning and audit trails become standard practice.
  • The organisation is no longer reliant on offline documents or duplicated file stores.
  • Backups can be automated
  • For some organisations, this might take the form of customised dashboards or record-management forms. For others, it may use platforms such as Adminer, phpMyAdmin, pgAdmin in hosted mode, or bespoke internal systems and low-code form builders.

    The key outcome is that data becomes centrally held, centrally maintained, and accessible in a structured way through the browser — allowing non-technical staff to work confidently with shared information.

    Recommended Implementation Order

  • Stage 1: Establish web hosting control (cPanel / Plesk / DirectAdmin) BEGINNER
  • Stage 2: Establish a communication layer (WordPress for documentation & publishing) BEGINNER
  • Stage 3: Experiment building lightweight task specific browser tools to reduce dependency of desktop utilities BEGINNER
  • Stage 4: Establish enterprise data backbone (PostgreSQL + PostGIS) ADVANCED
  • Stage 5: Establish spatial data publication (GeoServer / mapping clients) ADVANCED
  • Stage 6: Establish controlled data editing interfaces (admin dashboards / low-code) ADVANCED
  • Stage 7: Consider Client Portals VERY ADVANCED

  • Stage 1 – Provide simple web hosting management access for users – for example cPanel: Software that allows delegation of Simple Web Management Tasks to Domain Users

    cPanel is a platform (think administration dashboard panel) known in the trade as a web hosting manager – Web Hosting Management software is now so good that it provides a simple Web administration layer that is consistent across many cloud providers and which is learnable by most intelligent domain users. Importantly it allows domain users to have some agency over the management of simple tasks related to their infrastructure and applications. Many small to medium organisations rely on cPanel hosting environments to create applications and deploy databases. This allows applications and databases to be hosted and moved to other cloud providers either on cPanel or on a number of alternative Web Hosting Management Software alternatives.

    Here I give cpanel as an example but similar alternatives such as Plesk and DirectAdmin exist for which there are hundreds of cloud providers..


    Stage 2 – WordPress: Content Management Software perfect for Procedure Documentation or Public Outreach

    WordPress serves as a communication front-end in a digitally transformed organisation. WordPress as a content management system actually sits on top of a relational database, usually MySQL or Mariadb. It functions as a reliable publishing and engagement platform — ideal for sharing procedural notes, updates, and policy information with staff, partners, or the public seamlessly handling version control.

    Running typically on MySQL or MariaDB, WordPress offers a straightforward content management system that integrates easily into standard web hosting environments. Using cPanel, Plesk, or equivalent systems means routine administrative tasks — backups, SSL certificates, plugin updates — are simple and repeatable.

    In this structure, WordPress becomes the information delivery layer: the digital noticeboard where well-governed, database-backed systems meet accessible public communication.


    Stage 3 – Vibe Coding : Building lightweight task-specific browser tools to reduce dependency on desktop utilities and local IT

    By default cPanel will publish any file named index.html placed in the server directory named the same as the domain or sub-domain and depending on how you decide to setup cpanel you may have unlimited ability to setup sub domains which means unlimited potential applications.

    Experiment with your favourite AI software and asking it to write a simple html / javascript and css index.html file that can be used to merge pdf documents. Take this file and using cPanel place it on the server within the directory relating to your domain or sub domain. On any computer in the world now navigate to the domain url and hey presto that application is available. Javascript runs in the browser of the client machine so there is no issue with resources beyond the initial hit.

    Combine 2 PDF Vibe Coding Example


    Stage 4 – Postgres – Free Enterprise Database Provision

    Postgres has some of the best tooling for spatial data – a characterisitic particularly important for professions dealing with the built environment. Installation of postgres is easy and free but setting up web dashboards is a slightly more advanced topic. Generally the setup is harder than administration so I recommend you seek help with this process. Your IT section may wish to separate the server provision for this.


    Stage 5 – GeoServer: Sharing Maps and Spatial Layers

    Geoserver is an open source application designed to help districute spatial datasets, GeoServer adds a powerful visual layer. Again this is more advanced topic and again the initial installation and configuration is complex so please seek assistance before moving forward. Connected to the same PostgreSQL database, it serves data via WMS, WFS, or WMTS — industry-standard web mapping protocols.

    This means:

    Your GIS teams maintain a single authoritative dataset.
    Users can access maps in QGIS, MapLibre, or web apps without downloads.
    Styling and layers can be managed centrally and published instantly.
    Together, the database and map services form a robust data fabric where both tabular and spatial information are web-ready, discoverable, and always live.


    Stage 6 – Low Coding Tools – Build your own simple CRUD database systems and publish to your cpanel

    Up until now most of the suggestions have been largely open source. Tools that create Low Code CRUD applications tend not to be free and at this point you may wish to have a budget. Again this is a slightly more complicated topic as although usually using the tools is easy creating and configuring the environment to which you publish these and ensuring you can connect to the requisit databases is more advanced.

    Stage 7 – Client Portals
    Client Portals allow hundreds or thousands of people to benefit from your infrastucture possibly allowing you to magnify you efficiency by allowing clients to perform simple tasks. Such provision is however a serious undertaking and is beyond the scope of this article. Rest assured having the other stages in provides for the basis for this final stage

    Succession, Reliability and the Value of Proven Technology
    A key underpinning of this articles focus is succession and reliability — in other words, using technologies that are already widely adopted, thoroughly tested, and backed by large user communities.

    WordPress powers around 43% of all websites globally, while MySQL and MariaDB form the backbone of millions of web applications. PostgreSQL is consistently ranked among the top three database engines worldwide and is widely used in enterprise, public sector, GIS and high-reliability systems. Those databases are open source and free to install. Additionally your organisation already probably has SQL Server and Oracle that can link into bespoke web user interfaces in parallel to the systems already in place.

    Major hosting providers report uptimes above 99.9% for WordPress and MySQL-based environments, and PostgreSQL is known for its strong concurrency management, transactional integrity, and failover capabilities.

    By choosing these well-established platforms, organisations reduce risk, ensure continuity of knowledge, and make long-term system maintenance predictable and affordable.

    A Sustainable Digital Ecosystem
    The combination of a relational database, browser-based data editing, GeoServer for spatial publication, cPanel for hosting administration, and WordPress for public communication and procedure documentation provides a sustainable, transparent, and maintainable model for digital transformation.

    This stack enables enterprise-level data management without enterprise-level costs, while ensuring that:

  • All data changes are recorded and recoverable.
  • All users access the same single source of truth.
  • The public-facing narrative is clear, consistent and up to date.
  • Backup and Access security can be enforced.