❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

Security is a business capability, not a technical function

30 October 2026 at 12:04

WordPress security governance covers the decisions an organisation makes about who owns its platform, who can access it, how the software it depends on stays up to date, and which third parties and AI tools connect to it. In the enterprise estates we audit, most security incidents trace back to one of those decisions.

At Human Made, we work with global publishers, government departments and large enterprises. Across all of them, the organisations with the best security outcomes treat security as something the whole business maintains over time. Their results come from clear ownership, regular access reviews and a defined process for handling change.

This article explains where enterprise security risk starts, why it belongs to the whole business, and how to measure your organisation’s maturity. If you want the practical side first, our WordPress security page covers how Human Made secures enterprise platforms.

Is WordPress secure enough for enterprise organisations?

Yes, when organisations deploy and operate it to meet their security requirements. Many enterprise organisations run WordPress, including major publishers, universities, government agencies and financial services organisations such as Standard Chartered. Those platforms stay secure because their teams patch on a schedule, review who has access and control what gets installed.

WordPress does attract more public discussion of vulnerabilities than most proprietary platforms. That’s partly a matter of scale: it is among the most popular technologies on the web, so more people examine it. It’s also because when someone has fixed a reported issue in core, the WordPress Security Team publishes the details alongside the release. How a WordPress security release happens walks through that process from report to patch in more detail.

A proprietary CMS with the same number of flaws would rarely show them in the same way, because its review happens inside one vendor and customers depend on what the vendor chooses to disclose. A count of public disclosures measures scrutiny. To judge safety, you need to know how quickly fixes ship and how quickly installations apply them.

For an enterprise, the useful test is practical: can the organisation see every system the platform touches, name who manages each one, and respond when something changes?

Where do enterprise security risks come from?

Most security incidents on enterprise platforms start outside the CMS core. A typical estate depends on hosting infrastructure, third-party services, CRM and marketing integrations, analytics, custom code, user accounts and, increasingly, AI applications. Each of those adds a point of exposure.

In WordPress environments, most of the risk falls into four categories.

Third-party software

Plugins, integrations and external services usually carry the largest share of risk. A plugin that its developer maintained well at installation can lose that developer two years later, and an integration added for one campaign can stay connected long after the campaign ends. Without a review process for new additions and a record of what already runs, dependencies accumulate faster than anyone can assess them.

Access management

Enterprise sites rarely have only a handful of administrators. Editorial teams, marketers, regional teams, developers and external agencies all need some level of access, and permissions tend to grow. An agency keeps its login after a project closes, or an editor receives administrator rights to fix one problem and keeps them for years. Any of those accounts could give an attacker a route in.

Operational discipline

Delayed updates, undocumented customisations and unclear ownership weaken a platform gradually. They rarely look urgent on their own, so they tend to persist.

AI tools and new data flows

Teams now connect AI services to content repositories, customer data and internal systems, often quickly and sometimes without central approval. Each connection raises questions about what data the tool can read and where it goes, and about which vendor is now responsible for it.

With the right processes, an organisation can manage all four, and it would face the same four on any other CMS. Our Definitive Guide to Enterprise WordPress Security covers each of these risk areas in more depth, including the operational gaps that tend to build up unnoticed.

Why does WordPress security governance belong to the whole organisation?

Most security failures start with people and processes that no single technical team controls. Marketing chooses tools, regional teams commission microsites, procurement signs agency contracts and legal sets data-handling obligations. When IT alone owns security, every one of those decisions happens without it.

The consequences also reach well beyond IT. A breach on a public platform can trigger regulatory reporting, take revenue-generating services offline, and damage trust with customers and partners. Those outcomes land with the executive team, the board and the compliance function. Treating security as a business capability means the people who carry those consequences also help manage the risk.

In large digital estates, the problem is easy to see. An enterprise might run a main website, a dozen regional platforms, campaign microsites and an internal publishing environment, often on WordPress Multisite. When each owning team secures its property on its own terms, standards drift. One site might enforce single sign-on while another relies on shared passwords, or one team reviews plugins before installing them while another installs whatever the agency recommends. Over time, gaps open up between teams that nobody is responsible for.

WordPress suits this model because organisations can bring it inside their existing security frameworks. Teams choose their own hosting, connect the platform to their identity provider, apply their own access policies and run it through their own audit processes. That makes it possible to set one security standard and apply it across every property in the estate.

What does good WordPress security governance look like?

The organisations with the strongest results tend to have three things in common: named ownership, security built into normal delivery, and standards that apply across every site they run.

Named ownership

Uncertainty over who is responsible for what causes many security problems. As platforms grow, integrations get added and staff and priorities change, so decisions about patching, access reviews or vendor risk fall between departments and wait.

Strong organisations assign that responsibility explicitly, across technology, marketing, operations and external partners, and back it with identity and access management. WordPress supports this through its built-in roles and capabilities, and organisations can add single sign-on with their identity provider using a plugin or a platform layer such as Altis. Each person’s permissions then match their job, and administrators can revoke them centrally when that person leaves.

Security built into delivery

Security checks run on every change throughout a project. Automated scanning flags vulnerable plugins, themes and code while developers are still working on them, when an issue costs far less to fix than one found in a pre-release audit. Releases stop stalling on late reviews, and developers come to treat security as part of their own work.

Shared standards across every site

Shared standards and access control policies give multi-site organisations consistency without forcing every team into the same workflow. A central team defines the baseline: approved plugins, update windows, authentication requirements and the review process for new integrations. Regional and brand teams then build what they need on top of that baseline, and the central team can still see what’s running across the estate.

How does vendor lock-in affect WordPress security governance?

Dependence on a single vendor limits how quickly an organisation can respond when its security requirements change, and procurement teams often miss that cost.

Proprietary platforms often feel easier to govern. One contract covers the software, the infrastructure, the support process and the security controls, so the organisation knows who to call. It may have far less visibility of how the platform works internally, how the vendor handles vulnerabilities, or when a fix will ship, so its security posture rests partly on what the vendor chooses to disclose.

With WordPress, anyone can read and review the codebase. The WordPress project also works closely with some of the largest web hosts, network providers, CDNs and security research institutions, which gives it access to expertise no single vendor employs. Security teams can therefore read the code they are responsible for, follow how the project resolves issues, and make decisions from evidence.

That control becomes important when requirements change. A new regulation, an acquisition or an AI integration can each create security needs that didn’t exist when the contract was signed. On a closed platform, the organisation has to wait for the vendor’s roadmap to catch up, whereas on an open one it can change its hosting, architecture or processes on its own timetable.

The wider WordPress ecosystem helps here too. Enterprises can choose between many hosting providers, agencies, security specialists and support partners. If one relationship stops working, they can end it without replacing the platform or rebuilding their governance.

How is AI changing WordPress security governance?

AI increases the number of systems that can read an organisation’s content, knowledge and customer data, so security teams need a record of which tool connects to which system, and what it can read

Most AI tools need access to data to be useful. A content assistant draws on the editorial archive, a support agent on customer records, and a search tool on internal documentation. Information that used to stay inside one well-governed system now travels to several, and some of those systems are run by vendors the security team has never assessed.

A team might trial a tool to speed up production, find it helpful, and connect it to more systems before anyone asks what it can access. Repeat that across departments and the organisation loses track of where AI is in use and what data it touches.

Organisations should bring AI tools under the same governance as the rest of the platform, before those tools go live. For every AI tool in use, an organisation should know what information it can reach, who is accountable for it, and what risk assessment took place before anyone connected it.

WordPress gives security teams a solid basis for those answers. Its capability-based permissions model is granular and extensible, so administrators can give an AI integration exactly the access it needs and nothing more. Our WordPress AI page covers how Human Made approaches these integrations.

For a structured way to benchmark your organisation’s security maturity, download The Definitive Guide to Enterprise WordPress Security. If you’d like a second opinion on your platform and governance, talk to us about a WordPress security audit.

FAQ: Enterprise WordPress security governance

Yes. Publishers, universities, government agencies and financial services organisations run WordPress at enterprise scale. Like any CMS, its security depends on how teams host, govern and maintain it. Because its codebase is open, anyone can review it, and the WordPress Security Team publishes details of each vulnerability once it has been fixed.

The largest risks are third-party plugins and integrations, permissions that grow without review, delayed updates and unclear ownership, and AI tools with unchecked access to company data. Good WordPress security governance manages each of them.

It means the whole organisation shares ownership of security, including the teams that choose tools, commission sites, manage vendors and handle data, with clear accountability at each point. IT still runs the technical controls, while the rest of the business takes part in the decisions that create or reduce risk.

No. Anyone can review open-source code, and fixed vulnerabilities are disclosed publicly. With proprietary software, review happens mostly inside the vendor and customers rely on that vendor to disclose problems. A higher count of published vulnerabilities usually means more people are reviewing the code.

Keep a record of every AI tool in use, assign an owner to each, and assess what data it can reach before anyone connects it. Then grant each integration the minimum access it needs through the CMS’s permissions model, and review those connections as regularly as user accounts.

The post Security is a business capability, not a technical function appeared first on Human Made.

7 Steps to Bring AI Tools Under Security Governance on WordPress

30 October 2026 at 12:03

Without governance, unapproved AI tools will creep into your WordPress site over time, often through a series of small and seemingly innocuous decisions. Whether it’s an editor who wants to try a new assistant, or a developer who connects a model to the codebase, it’s natural for your team to want to adopt the tools that make their jobs easier. But it should never come at the cost of your security.

AI governance for WordPress is about giving teams clear rules to follow so they can adopt AI with confidence, and avoid sending sensitive information to unapproved tools. The seven steps below will show you how to find the AI tools already connected to your site and set limits on what each one can access.

What AI Governance for WordPress Means

AI governance for WordPress is about clarifying what AI tools can do and see on your platform covering access, data, review, and accountability.

WordPress now gives you a technical way to set some of those limits. WordPress 6.9 added the Abilities API, a standard way to register the actions a site can perform, each with an optional permission check. The API gives you the control point as your team still has to decide which abilities to expose, and to whom.

Step 1: Inventory Every AI Tool and Connection

Start by listing every AI tool that touches your WordPress environment:

  • Plugins with AI features
  • Browser extensions your editors use
  • API keys and connections to model providers
  • Agent and MCP connections to your site
  • Tools your agency or vendors use on your codebase

Watch out for any uses of shadow AI, where members of your team may have adopted tools without approval or visibility.

The goal here is to have one current register, with a named owner for every tool.

Step 2: Classify Tools by Risk and Data Sensitivity

Not every tool needs the same scrutiny. Sort each one by what data it touches and what it can do:

  • Low risk: suggests edits to public content and can’t change anything on its own.
  • Medium risk: reads unpublished or internal content.
  • High risk: publishes content, changes code or settings, or touches personal data.

The tier will dictate how much review a tool gets. For example, a low-risk writing assistant needs a quick check, but a high-risk agent with write access needs a full security review.

Step 3: Lock Down Access and Credentials

What an AI tool can reach decides how much harm it can do, so access is the first control to tighten.

  • Use least privilege. Scope each connection to specific actions rather than broad admin rights.
  • Treat AI agents as users. Give them their own accounts and roles, so you can trace and revoke their access.
  • Protect credentials. Store API keys in a secrets manager, not in code or plugin settings. Rotate them regularly and whenever staff change.
  • Remove what you don’t use. Delete dormant connections and unused keys.

Step 4: Set Rules for What Data AI Can Use

Decide in advance what information can go to a third-party model. A simple split works well:

  • Usually fine: published, public content.
  • Needs approval: unpublished drafts and internal documents.
  • Restricted: personal data, client confidential material, and anything under regulation.

Check each provider’s terms for whether they train on your data and how long they keep it. Then write the rules in plain language that editors and developers can follow.

Step 5: Keep Humans in the Approval Path

AI can play a part, but sign-off should always come from a human.

Build review into the workflow for anything high-impact:

  • Publishing content
  • Deploying code
  • Changing permissions or settings

Approval only works when the reviewer has the authority and the time to say no. A rubber-stamp step adds risk because it creates false confidence.

Done well, AI still speeds up the work, and a named person signs off on the result.

Step 6: Log and Monitor AI Activity

You can’t govern an AI tool whose activity you can’t trace. Record which tool did what, when, and under which account.

Then watch for unusual patterns:

  • Sudden spikes in requests
  • Activity at odd hours
  • Access to content a tool shouldn’t touch

Add rate limits and cost caps so a misconfigured tool can’t run up a bill or flood your platform. Keep logs long enough to support an investigation. This is the same audit-trail discipline we recommend for agencies, and it applies just as well to your internal tools.

Step 7: Assign Ownership and Review Regularly

Lack of ownership often contributes to governance failure. To avoid this, name an accountable owner, typically a senior leader in digital or security, and give them the authority to approve and retire tools.

Then put the basics in writing:

  • A short AI usage policy that staff can read in minutes
  • An incident plan covering how to revoke access, roll back changes, and notify the right people
  • A review schedule, quarterly at minimum, plus a check after any major tool update or WordPress security release

Frameworks can help you structure this. The NIST AI Risk Management Framework offers a starting point, and OWASP’s guidance on LLM application risks covers the specific threats worth planning for.

AI Governance Checklist at a Glance

StepKey actionTypical owner
1. InventoryList every AI tool, key, and connectionDigital or IT lead
2. ClassifyTier tools by data and capabilitySecurity lead
3. AccessApply least privilege and manage keysEngineering
4. Data rulesDefine what AI can and can’t useSecurity and legal
5. ApprovalRequire human sign-off on high-impact actionsEditorial and engineering
6. MonitorLog activity and alert on anomaliesEngineering and security
7. OwnershipAssign an owner and review regularlySenior leadership

Governance Makes AI Usable at Scale

A one-page register of your AI tools, with an owner against each one, is a useful first step toward seeing your real exposure. Start with Step 1 this week.

Once your register is in place, The Definitive Guide to Enterprise WordPress Security shows how AI governance fits into your wider security picture. Its self-scoring maturity assessment covers governance, access controls and AI readiness, so you can benchmark where your organisation stands and decide what to tackle next.

FAQ: AI Governance for WordPress

It can be, with the right controls. Vet each plugin carefully and limit its access. Risk depends on what the tool can read and change.

Shadow AI refers to any AI tools that staff use without approval or visibility. It’s hard to protect data or enforce rules for tools that you don’t know exist.

One accountable senior owner, usually in digital, IT, or security, supported by input from legal, editorial, and engineering.

Yes, if anyone on your team uses AI on your platform. A short, clear policy sets expectations and gives you something to point to when questions or incidents arise.

Start with an inventory, then apply least-privilege access, separate accounts for agents, and scoped permissions. Remove any connection you can’t justify, and log what remains.

The post 7 Steps to Bring AI Tools Under Security Governance on WordPress appeared first on Human Made.

Open Source vs Proprietary CMS Security: What Enterprise Teams Should Know

30 October 2026 at 12:03

Key takeaway: In the open source vs proprietary CMS security debate, open source holds up well in the enterprise space. WordPress keeps vulnerabilities private until a fix is ready, then delivers it through automatic updates by default. With either model, how your team runs the platform is what matters most.

Enterprise security teams often ask us if open source is safe enough. The short answer? Yes.

Truth be told, we’re a WordPress agency, so we’re not totally neutral but we’ll show you our reasoning so you can understand our take.

Keep reading for a full comparison on open source vs proprietary CMS security covering how each model handles vulnerabilities, and what enterprise teams do to keep either one strong.

Is Open Source Less Secure Than Proprietary Software?

No. Maintenance is the real determining factor in a platform’s security level, including how fast fixes ship and how quickly customers apply them.

With open source, your security team and independent researchers can inspect the code, and a global community of contributors reviews it continuously. That review feeds a structured process for reporting and fixing vulnerabilities, described below.

How WordPress Handles Vulnerability Reports

Researchers report most vulnerabilities privately, through the WordPress Security Team and its HackerOne program. The team verifies each report and triages it in a private workspace, separate from public development tools.

The team ships critical fixes as standalone security releases while lower-severity fixes wait for the next scheduled release.

For serious issues, major hosts and security vendors get advance notice. Protection can be in place before the fix goes public. WordPress 7.0.2, released in July 2026, shows this working. The security team worked with hosts and CDN providers to put mitigation in place across tens of millions of sites before the release went public.

Once a fix ships, the team publishes an advisory that credits the researcher. Serious issues may also receive a CVE, which lets enterprise vulnerability-management tools track them consistently. Sites with automatic background updates, the default for minor and security releases, can receive the fix within hours without anyone taking action. Our post on how a WordPress security release happens walks through each stage.

WordPress is one of the most widely used technologies on the internet, so its vulnerabilities get announced and discussed in public. That can make it appear as though WordPress has more issues than other platforms but that’s really just a side-effect of transparency. A global community of contributors and security researchers reviews the code continuously.

What Vendor-Managed Platforms Do Well

Proprietary CMS vendors offer a single accountable company and a contract that defines responsibilities. Many also manage patching for you, which suits teams with limited security capacity.

The main difference from open source is how much your team can see. With a proprietary platform, you rely on the vendor’s advisories to learn what each fix changed, and you usually can’t inspect the code to check for yourself.

Open Source vs Proprietary CMS Security: Side by Side

FactorOpen source (e.g. WordPress)Proprietary
Code visibilityYour team and independent researchers can inspect itLimited to the vendor and approved parties
Vulnerability handlingPrivate triage, then a public advisory after the fixVaries by vendor
Patch timingFixes ship quickly, and automatic updates can apply themThe vendor sets the schedule
Who applies the fixYour team or agency, or automatic updatesOften the vendor, depending on the contract
Third-party codePlugins and themes need review before launchAdd-ons and integrations need the same review
Independent verificationYour team can test and audit directlyDepends on what the vendor allows
AccountabilityShared between your team and your agency or hostConcentrated with the vendor
Exit optionsYou can change agency or host and keep the platformChanging vendor might mean replacing the platform

Four Ways Enterprise Teams Keep WordPress Protected

Open source gives you control. Enterprise teams use it in four ways.

  1. Test updates in staging before they reach production. Enterprise teams often control automatic updates so that regression testing and change control happen first.
  2. Review plugins and themes before launch, and again at each major update. WordPress plugin security starts with deciding which code you allow.
  3. Give each user and integration the minimum access it needs, and review permissions regularly.
  4. Name an owner for patching and another for incident response.

Our WordPress security page explains more about how we handle security on client platforms.

Questions to Ask Any Vendor or Agency

These questions work for open source and proprietary platforms. For more useful questions to ask when in the prospecting stage of agency selection, check out our article on questions worth asking before choosing a WordPress agency.

  • How do you handle vulnerability reports, from first report to fix?
  • How fast do you patch, and who applies the fix?
  • How do you vet third-party code?
  • What audit trails and monitoring exist?
  • Who owns incident response, and what are the response times?

How AI Is Raising the Value of Fast, Coordinated Patching

AI agents can now exploit known vulnerabilities quickly, so the time between a published fix and a protected site matters more. This is why WordPress keeps unpatched issues in a private workspace and gives hosts advance notice. It’s also why automatic updates narrow the gap.

Teams also need to know how their agency uses AI on their codebase. We cover this in how WordPress agencies use AI and what clients should ask.

Next Steps for Enterprise Security Teams

To conclude, when it comes to open source vs proprietary CMS security, both models can meet enterprise requirements. WordPress adds transparency, a mature disclosure process and exit options. Your choice depends on your team’s capacity to run the platform, or to work with an agency that does.

If you’re weighing up that decision, The Definitive Guide to Enterprise WordPress Security goes deeper into the governance and operational practices that keep a platform secure. Its self-scoring maturity assessment shows where your organisation stands today and where to improve next.

FAQ: Open Source vs Proprietary CMS Security

Yes, when the platform gets patched promptly and governed well. Open source adds public review and a mature disclosure process. Your team still decides how quickly it applies updates and who has access.

Yes. WordPress handles serious vulnerabilities privately and gives major hosts advance notice before a fix goes public. Enterprise teams add staged updates and controlled permissions on top.

Not automatically. They offer a single accountable vendor and often managed patching. You get less visibility into the code and into what each fix changed. Either model can be secure with good maintenance.

Responsibility is shared. The WordPress Security Team handles core vulnerabilities. Your agency or internal team looks after your implementation, and your host looks after the infrastructure. Name an owner for each.

Yes. No single vendor owns the platform, so you can change agency or host and keep it. Proprietary platforms often have several implementation partners too, but changing vendor means replacing the platform.

The post Open Source vs Proprietary CMS Security: What Enterprise Teams Should Know appeared first on Human Made.

How a WordPress Security Release Happens, From Report to Patch

30 September 2026 at 19:48

Most site owners only see one part of the process that results in a new version of WordPress being released that fixes a security vulnerability: a dashboard notification that reads “An updated version of WordPress is available”. That’s intentional, the software is built to “just work”. Everything before that notification happens behind the scenes, often over days or weeks. The process might start with a report about a weakness from a security researcher, proceed through verification, fixing the bug, testing, and subsequent coordination with some of the world’s largest web hosts and service providers. All activity that stays mostly outside of public view.

The WordPress security release process runs through a consistent set of stages: report, verify, triage, patch, test, coordinate, release, and notify. A critical severity fix may ship within hours, while lower severity issues wait for the next scheduled release, but the release and deployment process handles security issues at the speed that enterprise security teams depend on.

As one of the most widely used technologies on the internet, vulnerabilities in WordPress are announced, scrutinised, and discussed publicly. While this can create the impression that WordPress experiences more security issues than alternative platforms, it also reflects one of the fundamental strengths of open-source software: transparency. Potential issues are exposed to continuous review by a global community of contributors, security researchers, agencies, hosting providers, and enterprise users. With the rise in cybersecurity capabilities of frontier AI agents, this transparency is more important than ever.

Where WordPress Vulnerability Reports Come From

Many security issues in WordPress are responsibly reported to the WordPress Security Team via its well-established vulnerability disclosure program on HackerOne. A mixture of human review and AI augmentation results in each report being prioritised and routed to the appropriate development team accordingly.

Verifying and Triaging the Report

Not every submission of a security vulnerability turns out to be exploitable. Once the team confirms an issue is real, they assess how serious it is. Some issues can wait for the next scheduled release. Others need to move immediately.

That assessment happens inside a private workspace, separate from WordPress’s public development tools. This is because tracking an unpatched vulnerability in the open would hand attackers and their AI agents the same information the security team is racing to fix.

Immediate Release or Scheduled Release? How WordPress Decides

Severity determines the release path. The team pushes a critical issue out as an immediate, standalone security release, skipping the normal cadence. The risk of waiting outweighs the disruption of an out-of-cycle update.

A minor issue waits for the next regularly scheduled release instead, bundled alongside other fixes. That’s a risk-management decision. The team weighs exploitability and real-world impact against the cost of pushing an emergency release across millions of sites.

Coordinated Disclosure With Hosts and Security Vendors

The WordPress open source project has a uniquely close relationship with some of the largest web hosts and platform providers in the world, due to its ubiquity and the many members of the WordPress community who work for those companies. WordPress operates a private discussion forum for some of these companies so they can securely discuss upcoming fixes and plan mitigations in advance.

When a more serious vulnerability occurs, the fix doesn’t move straight from ready to public. Major hosting providers, CDNs, and web application firewall vendors are given advance notice to put protective measures in place prior to a security release being made available publicly.

WordPress 7.0.2, released in July 2026, is an example of this process working as intended. The WordPress security team worked closely with web hosts and CDN providers to put mitigation in place across tens of millions of WordPress websites before the release was made publicly available, due to the severity of the issue that was fixed. With the rise of autonomous AI agents that can quickly exploit known issues, this is more important than ever.

Publishing the Advisory: The Announcement Process

Once a fix ships, the team publishes an advisory on the WordPress.org News site. It details what was fixed and how serious the issues were. A CVE – a standardised public identifier that lets security tools, scanners, and enterprise vulnerability-management systems track the issue consistently – may be published for particularly severe issues.

The advisory will also credit the researcher who reported it. Being publicly credited builds a researcher’s reputation, which incentivises them to report privately rather than go public first.

How the Fix Actually Reaches Your Site

Administrators who haven’t turned on automatic updates will see a dashboard prompt to update manually. They’ll also be given a summary screen that summarises what changed. 

For sites with automatic background updates turned on (the default for minor and security releases) the fix will be completed without any action needed. The administrator simply gets a confirmation email once it’s done. These automated updates allow a large share of the WordPress ecosystem to gain protection within a matter of hours after a fix ships, removing the need for an individual site owner to notice a notification and act on it before an attacker does.

What This Means for Enterprise WordPress Security Teams

For a single site, this automatic process is usually sufficient. However, Enterprise environments tend to need something more substantial. Staging environments, regression testing, and change-control processes have to run before anything touches production. That’s why many enterprise platforms prefer to disable or tightly control automatic updates. 

Enterprise teams need their own patch verification and rollout discipline whenever there is a new WordPress security release. However, the WordPress Security Release process itself is transparent enough about how a fix moves from a researcher’s report to a trusted release, to allow enterprise teams to manage each release with confidence and understanding. 

A reliable patching process is only one part of securing WordPress at enterprise scale. The Definitive Guide to Enterprise WordPress Security covers the governance, operational and AI-readiness questions around it, and includes a self-scoring maturity assessment to show where your organisation stands.

FAQ: WordPress Security Release Process

Mostly through responsible disclosure. Researchers report issues privately, either via WordPress’s HackerOne program or directly to the security team, instead of publishing them immediately.

It depends on severity. The team can patch and release critical issues within days as an immediate security release. Minor issues usually wait for the next regularly scheduled release.

Yes, by default, for minor and security releases. Administrators can disable automatic background updates, and many enterprise environments do this to test changes before deployment.

The team treats critical issues as serious enough to justify an immediate, standalone release outside the normal schedule. Minor issues wait for the next scheduled release alongside other fixes.

The security advisory names the researcher who responsibly disclosed the issue, reinforcing the incentive to report privately rather than publish vulnerabilities publicly.

The post How a WordPress Security Release Happens, From Report to Patch appeared first on Human Made.

Why critical thinking matters in agencies

23 September 2026 at 10:57

Critical thinking in agencies means questioning assumptions. It means weighing evidence. It means reasoning through a decision before committing to it, rather than accepting the first plausible-sounding answer just because it arrived quickly. And it matters more now than it did five years ago. Templates, automation, and AI-generated drafts increasingly shape the daily judgement calls an agency makes. It has never been easier to mistake a fluent answer for a correct one.

This article sets out why critical thinking matters. It covers what the habit looks like in day-to-day agency work, and how teams can build it back in.

This isn’t an argument against automation, templates, or AI tools. All three have a legitimate place in how agencies deliver work efficiently. It’s an argument for keeping a deliberate human check in the loop. The cost of removing that check is higher than it first appears, and it tends to surface much later than the decision that caused it.

When technology promises to think for us

The World Economic Forum’s Future of Jobs research has consistently placed critical thinking near the top of the skills employers expect to matter most. Critical thinking and problem-solving top the list of skills employers believe will grow in prominence. That ranking has held steady since the Forum’s first report in 2016.

This consistency is worth pausing on. It suggests the demand for critical thinking in agencies isn’t a passing trend tied to one technology cycle. It’s a structural response to how quickly information, tools, and expectations change.

Agencies sit in an unusual position here. Clients often pay not just for execution but for judgement, and judgement is precisely what critical thinking protects. A team can defer entirely to whatever a template, a process document, or an AI system produces. But without pausing to check that output actually fits the situation, the agency stops adding the one thing a client can’t easily get elsewhere.

What this looks like in day-to-day agency work

Critical thinking rarely announces itself dramatically. It tends to show up as small, repeatable habits in how a team reaches a decision, not a single heroic moment of insight. In client-facing agency work, it tends to include the following.

  • Asking why before how. Pause before execution to check that the underlying assumption behind a brief, a recommendation, or a plan is actually sound.
  • Separating correlation from causation. Notice when two things happened together without immediately assuming one caused the other, especially when reporting results back to a client.
  • Actively seeking disconfirming evidence. Look for the data point, the client, or the colleague’s opinion that challenges the current plan, rather than only gathering support for a conclusion already reached.
  • Distinguishing a confident answer from a correct one. Fluency and confidence, whether from a person or an AI system, are not the same thing as accuracy.
  • Applying the most scrutiny where a mistake would be most costly. Don’t spread the same shallow level of review evenly across every decision.

None of these habits are dramatic on their own. That’s exactly why they’re the first thing to slip when a team is moving fast.

AI and critical thinking: why the two now depend on each other

People often frame AI and critical thinking as opposites. Using one, the thinking goes, means giving up the other. The more accurate framing is that AI has made critical thinking a precondition for using the technology safely, not a nice-to-have alongside it.

Generative AI systems are remarkably good at producing fluent, confident-sounding output. That fluency is exactly what makes uncritical reliance on them risky. An AI system has no internal sense of when it has got something wrong. Catching that falls entirely to the human reviewing the output. When a team treats AI-generated material as a finished answer rather than a first draft worth interrogating, the habit of critical evaluation weakens from simple lack of use.

We’ve written before about how agencies use AI internally, covering quality, safeguards, and transparency. The underlying argument there is the same one this piece makes: those three things are critical thinking, applied systematically to AI output.

Avoiding cognitive bias in decision making

Avoiding cognitive bias in decision making is one of the more concrete, evidenced reasons critical thinking earns its place in agency work. Cognitive biases such as confirmation bias, anchoring, and overconfidence quietly distort judgement long before anyone notices. They affect experienced decision-makers just as much as inexperienced ones. That’s part of why they’re so persistent.

Research summarised by McKinsey on behavioural strategy found that organisations which actively work to reduce bias in major decisions tend to see meaningfully better outcomes. That work draws on behavioural economics research into the limits of rationality, and how systematically decision-makers deviate from purely rational calculations.

That evidence matters for agencies specifically. Many of the recommendations an agency makes carry real stakes, whether about a platform choice, a migration approach, or a content strategy. An unexamined bias can quietly steer a client toward the wrong outcome.

A few practical steps help counteract this. Assign someone in a review to deliberately challenge the prevailing view. Separate when a team makes a recommendation from when it needs to deliver it. Treat any option that arrived first or loudest with a little more scepticism.

The cost of skipping it

The cost of skipping critical thinking in agencies rarely announces itself at the point a team takes the shortcut. It tends to surface later, once the consequences have compounded into something harder to unpick.

A team mistakes a confident pitch for genuine substance, and a hiring or vendor decision goes ahead on that basis. A plan goes unchallenged in a meeting because no one wants to be the person who slows things down, even when several people privately have doubts. A team ships AI-generated material to a client without checking it against the underlying facts, because it read fluently. The same mistake keeps recurring across projects, simply because no one paused long enough after the first instance to ask why.

Individually, each of these looks like a minor lapse. Collectively, they tend to be the actual root cause behind the moments a team looks back on and asks how they missed something so avoidable.

Building the habit back into how teams operate

Critical thinking skills in the workplace are a practice, not a fixed personality trait. A person or a team can deliberately reintroduce them, even after they’ve slipped. A few concrete habits tend to make the most difference.

  1. Build in a pause before sign-off. Ask a single question, such as what would have to be true for this to be wrong. It costs very little time and catches a surprising number of avoidable errors.
  2. Assign a deliberate challenger. Rotate responsibility for pressure-testing a plan across a team. It normalises disagreement as routine, rather than personal.
  3. Treat AI output as a first draft, not a finished answer. Review AI-generated work the way an experienced editor reviews a junior colleague’s first pass. Keep the habit of scrutiny active, not dormant.
  4. Separate the decision from the deadline. Decouple when a team needs to decide from when the work needs to ship, wherever that’s possible. It reduces how many decisions get made under artificial time pressure.
  5. Keep an honest record of past mistakes. A simple, ongoing log, reviewed periodically rather than filed away, makes the case for slowing down concrete rather than theoretical.

How to evaluate a WordPress agency for critical thinking, not just capability

Anyone working out how to evaluate a WordPress agency tends to focus first on technical capability, delivery process, and security credentials. All three matter a great deal. But critical thinking in agencies is one of the clearest, most practical signals of whether a prospective partner will actually serve an organisation well, rather than simply agreeing with whatever brief lands on their desk.

A partner willing to push back on a flawed requirement is demonstrating exactly this. So is one who asks why before jumping straight to how, or says plainly that a proposed approach isn’t right. These are the habits this piece describes above, under real commercial pressure rather than in the abstract.

We’ve explored this in more depth in what to evaluate when choosing an agency, which sets out the four pillars we think matter most: technical capability, delivery maturity, security and governance, and strategic alignment. Critical thinking runs underneath all four. A partner can score well against every documented pillar and still fail to apply real judgement when a client’s situation doesn’t quite match the template.

Critical thinking in agencies isn’t a soft skill sitting alongside the real work. It’s the difference between a decision that happens to turn out well and one an organisation can actually rely on. The more useful question usually isn’t whether something looks right at first glance. It’s why you believe it actually is.

FAQ: Critical Thinking in Agencies

It’s the discipline of evaluating information, assumptions, and recommendations on their actual merits. It means not accepting them simply because they arrived confidently, quickly, or from an authoritative-sounding source.

Because AI and critical thinking now depend on each other, rather than sitting in opposition. Generative tools can genuinely widen the range of options a person considers. But that only holds if the human reviewing the output keeps questioning it.

Through small, repeatable habits practised consistently. Pause before sign-off. Actively seek out disconfirming evidence. Assign someone to challenge the prevailing plan. Treat both AI output and expert opinion as a starting point, not a settled conclusion.

Cognitive bias describes the specific, largely unconscious distortions, such as confirmation bias or anchoring, that quietly skew judgement. Critical thinking is the broader, deliberate practice that catches and corrects for those distortions.

Look for evidence that the agency questions a brief rather than simply executing it. Look for a team that asks why an approach is right for the specific situation, and one willing to disagree with a client when the evidence points elsewhere.

The post Why critical thinking matters in agencies appeared first on Human Made.

How WordPress Agencies Use AI — and What Clients Should Ask About It

16 September 2026 at 15:20

Most WordPress agencies now use AI somewhere in their workflow. But the real question isn’t whether an agency uses AI. It’s where, how carefully, and what still requires a human to sign off.

This matters more than it might seem. AI genuinely reduces repetitive work, but it doesn’t replace judgment. The agencies worth hiring can explain that difference clearly. Below, we break down how WordPress agencies use AI in practice, where it doesn’t belong in enterprise delivery, and the questions worth asking any agency about their approach.

Where AI Actually Shows Up in Agency Work

Code generation and scaffolding

AI coding assistants generate boilerplate, scaffold new components, and speed up repetitive implementation work. Agencies increasingly use these tools during development, particularly for well-understood, low-risk code. They don’t use them for the architectural decisions that shape how a platform holds up over time.

QA and testing

Visual regression testing and automated QA checks increasingly rely on AI to flag unexpected changes across a site. This catches issues that would otherwise require a person to manually compare screenshots page by page. It speeds up testing, but a person still has to decide whether a flagged change actually matters. The WordPress core handbook on testing sets out how testing rigor works at the platform level, AI-assisted or not.

Content migration and modeling

Migrating a large, messy legacy site into a clean content model plays to AI’s strengths: repetitive, pattern-matching work at scale. AI tools can map old content types, auto-tag content, and flag inconsistencies far faster than a person working through the same site manually.

Documentation

AI tools can draft technical documentation directly from code, which teams then review and refine. This keeps documentation from falling behind development, a common failure point on long-running platforms.

Research and internal operations

Many agencies use AI for competitive research, accessibility audits, meeting notes, and early drafts of proposals or reports. Clients rarely see any of this, and that’s generally the point. It’s productivity tooling, not a deliverable.

Where AI Doesn’t Belong in Enterprise Delivery

AI struggles with decisions that carry real consequences if they go wrong. Strong agencies draw a clear line here instead of letting AI creep into places it shouldn’t be — a distinction we cover in more depth in our Definitive Guide to Choosing an Enterprise WordPress Agency.

Architecture and technical decisions

Choosing how a platform scales, how integrations connect, or when to take on technical debt requires context AI doesn’t have: the organization’s history, its constraints, its future plans.

Governance and compliance judgment calls

Accessibility, security, and regulatory requirements involve trade-offs specific to an organization’s risk tolerance. That’s a human decision, not something to automate. The W3C’s Web Accessibility Initiative guidelines show the kind of nuanced, context-dependent standard that still needs human interpretation.

Client-facing strategic recommendations

Advice that reflects real judgment about a client’s specific situation should come from someone who understands that situation, not a generated summary.

Agencies that treat AI as a tool for reducing grunt work, rather than a replacement for expertise, tend to be the ones worth trusting with a serious platform. We describe the same pattern in our breakdown of WordPress agency red flags and green flags: confidence and specificity matter more than the tool itself.

Safeguards for Responsible AI Use

Using AI well isn’t just about where an agency applies it. It’s about what surrounds that use. A few safeguards worth looking for:

Human review before anything ships. A person should review AI-generated code, content, or documentation before it reaches production or a client, particularly for anything that touches architecture or security.

Clear data handling policies. Client data shouldn’t go to third-party AI tools without a clear understanding of what happens to it, and under what terms. This matters especially for platforms handling sensitive or regulated content.

Some form of audit trail. When AI plays a role in a decision, someone should be able to trace what it generated, what a person reviewed, and what changed.

Written internal guidelines. Agencies with a genuine AI policy, even a simple one, tend to apply it more consistently than those making it up as they go.

Questions to Ask About AI Use

A short list of questions that tend to reveal how seriously an agency takes this — and a natural extension of the broader questions worth asking before choosing a WordPress agency:

  • Where in your workflow do you currently use AI?
  • What does a person review before it reaches me?
  • Do you ever send my data to a third-party AI tool, and under what terms?
  • What would you never let AI decide on its own?
  • What’s changed about how you work because of AI, and what hasn’t?

Vague or evasive answers here are worth paying attention to. Agencies that have thought this through can usually answer quickly and specifically, because they’ve already had to define the boundaries for themselves.

Why the Best Use of AI Is Invisible

The agencies getting real value from AI tend to describe it in fairly unglamorous terms: less time on repetitive work, more time on the decisions that actually require expertise. That’s a productivity story, not a marketing one.

This lines up with how we think about agency selection more broadly. The details that actually predict a good partnership rarely make for an exciting pitch, a theme we explore further in the total cost of choosing the wrong agency. AI works the same way. If an agency’s AI story sounds more like a sales pitch than a workflow decision, take note.

Choosing an Agency With Your Eyes Open

How WordPress agencies use AI is changing fast, but it hasn’t changed what actually matters in choosing one: judgment, transparency, and a clear sense of where human expertise still needs to lead.

For a broader framework on evaluating agency partners — including questions to ask, red flags to watch for, and a full evaluation scorecard — see our Definitive Guide to Choosing an Enterprise WordPress Agency.

FAQ: How WordPress Agencies Use AI

Ideally, yes. Agencies confident in how they use AI generally have no reason to hide it, and transparency here is a reasonable proxy for how seriously they take the underlying practice.

It depends on where and how they use it. Reviewed, AI-assisted work is generally low-risk. AI making unreviewed decisions about architecture, security, or governance is a different matter, and worth asking about directly.

With AI-assisted work, a person uses AI as a tool within their own process, then reviews and takes responsibility for the result. AI-generated work implies less human involvement, and in an enterprise context, that distinction matters.

This varies. Some agencies treat AI tooling as part of their standard process, similar to any other software they use. Others may factor efficiency gains into pricing. It’s a reasonable question to ask directly during procurement.

The post How WordPress Agencies Use AI — and What Clients Should Ask About It appeared first on Human Made.

How to Evaluate an Enterprise WordPress Agency: The 4 Key Pillars

14 September 2026 at 15:09

Knowing how to evaluate an enterprise WordPress agency comes down to four things that rarely show up clearly in a pitch. Those four things are technical capability, delivery maturity, security and governance, and strategic alignment. A visually impressive site means very little if the platform becomes difficult to scale, maintain, or govern six months after launch. That’s exactly why these four areas matter more than the portfolio ever will.

Why a Pitch Alone Won’t Help You Evaluate an Enterprise WordPress Agency

Most enterprise WordPress agencies look similar on the surface. Polished case studies, recognisable client logos, and a confident timeline tend to appear in almost every proposal you’ll read. However, none of that actually tells you how an agency performs once a project gets hard. Requirements shift, timelines tighten, and the platform eventually has to hold up under real operational pressure. In fact, the cost of getting this decision wrong rarely shows up at launch. It tends to surface months or years later. That’s precisely why learning how to evaluate an enterprise WordPress agency means looking well past the sales process itself.

These four pillars exist to surface exactly that. Each one focuses on a different part of how an agency actually operates once the contract is signed and the real work begins.

Looking for a real deep dive into choosing a WordPress Agency? Check out The Definitive Guide to Choosing a WordPress Agency, complete with evaluation scorecard.

The 4 Pillars to Evaluate an Enterprise WordPress Agency

Below, we break each pillar down into what it actually covers and what you should ask about. That way, you can compare agencies on substance rather than presentation alone.

Pillar 1: Technical Capability

Technical capability describes whether an agency can explain, clearly and without unnecessary jargon, how their platform will hold up under real pressure. Traffic grows, editorial teams expand, and teams add new integrations over time.

Architecture and Scalability

Enterprise platforms need to support growth without becoming fragile. That means handling increasing traffic volumes, new integrations and workflows, regional or multisite expansion, and future migrations without requiring a rebuild each time. A strong architecture creates flexibility without introducing chaos. Look for teams that think in systems rather than individual features, and who can explain performance and long-term maintainability in practical terms instead of jargon.

Engineering Standards

Good engineering practices rarely attract attention when everything works smoothly. Their absence, however, becomes obvious very quickly once something breaks. Ask how the team reviews code, how they test releases before deployment, and what deployment workflows they rely on. Also ask how they manage technical debt as the platform grows and requirements change. Mature engineering teams maintain strong internal processes, clear coding standards, and structured QA. Importantly, they can also explain these practices clearly to non-technical stakeholders, not only to other engineers.

Integrations and Extensibility

Enterprise WordPress platforms sit inside busy digital ecosystems. CRM data, DAM assets, analytics, identity management, and marketing automation all connect in. Each connection adds real value while also introducing another point of dependency. As a result, a capable agency won’t treat integrations as a box-ticking exercise. Instead, they’ll want to understand how data actually moves, who owns it, and what happens when a service fails unexpectedly. Saying “yes, we can integrate that” is easy for almost any agency to claim. Designing an integration that stays maintainable two years later, on the other hand, takes real, hard-won experience.

Hosting and Operational Resilience

Infrastructure decisions shape a platform’s stability long after the initial launch has come and gone. So it’s worth asking how the team structures environments, how they manage releases day to day, and what monitoring and alerting they rely on. It’s also worth asking how they handle incidents and rollbacks when something goes wrong. These details can feel secondary during procurement. In reality, though, they often determine whether a platform stays reliable once it’s under genuine operational pressure. Ultimately, if an agency can only describe what they’ll build, that gap is worth noting. What matters more is whether they can explain how they’ll keep it maintainable two years from now.

Pillar 2: Delivery Maturity

Delivery maturity is about process rather than raw skill alone. Large enterprise projects rarely fail because of one single bad technical decision. Instead, they tend to break down through weak communication, unclear ownership, or planning that was unrealistic from the start.

Discovery and Planning

The quality of discovery usually determines the quality of everything that follows during delivery. Strong agencies spend real time understanding organisational structure, existing workflows, dependencies, and internal constraints before jumping to proposed solutions. They do this by asking difficult questions and identifying risks well before those risks become genuinely expensive. Admittedly, that approach can feel slower at the start of a project. In practice, though, it tends to create faster and cleaner delivery once the real work is underway. Consequently, it’s worth being cautious of agencies that move quickly toward estimates or technical recommendations without first understanding the environment they’re stepping into.

Team Structure and Accountability

One of the simplest and most important questions in enterprise delivery is also one of the most revealing: who actually owns what? Strong agencies define these responsibilities clearly from the start. That covers who leads delivery, who owns technical direction, how they maintain continuity across long projects, and what happens once scope changes partway through. Meanwhile, it’s worth paying close attention to how agencies describe their own teams during these conversations. Mature organisations tend to describe collaborative structures and shared ownership. Less mature ones, by contrast, lean heavily on individual personalities or senior leadership visibility during the sales process itself. That difference tends to become obvious fairly quickly once actual delivery begins.

Documentation, QA, and Release Workflows

It’s worth evaluating how the team tests releases, how they document decisions along the way, and how they structure governance and escalation paths. Experienced agencies introduce enough structure to keep projects moving without creating unnecessary bureaucracy. Instead, they maintain clarity and control while still keeping delivery moving at a reasonable pace.

Long-Term Support

Enterprise platforms don’t simply stop evolving once they launch. Content models expand, integrations change, and teams grow considerably over time. So it’s worth asking directly how post-launch support actually works, what SLAs exist, and how roadmap planning happens. It’s also worth asking whether support tends to be proactive or purely reactive once problems arise. Above all, the strongest agencies design for this reality from the start. They don’t treat it as an afterthought once they’ve already signed the contract.

Pillar 3: Security and Governance

Agencies can’t bolt governance onto a platform after launch. It has to be part of the platform’s design from day one if it’s going to hold up under real inspection. Enterprise platforms operate under constant scrutiny, which means security, accessibility, compliance, and permissions all need genuine consideration well before a release ever reaches production.

Ask the agency directly how they handle security reviews and what actually triggers them. Ask how they manage access and permissions across large editorial teams, and how they test and approve releases before they go live. It’s also worth asking whether compliance requirements shape delivery workflows from the start, rather than only appearing as a check at the very end.

Accessibility deserves particular attention within this pillar. Many agencies still treat accessibility as a late-stage QA task rather than a core part of design and engineering. That approach rarely scales well as a platform grows. Instead, strong partners embed accessibility directly into design systems, structured content models, and testing workflows from the very outset. They treat adherence to standards such as WCAG as an ongoing operational discipline rather than a one-off checklist exercise.

Overall, mature agencies build governance directly into the platform as a structural decision from the start. Less mature ones only address it once they’ve already built the platform and problems start appearing.

Pillar 4: Strategic Alignment

The strongest agency relationships feel genuinely collaborative rather than purely transactional. Good agencies don’t simply execute whatever requirements land on their desk. Instead, they actively help organisations make better decisions. That means challenging unrealistic timelines, identifying hidden risks early, aligning technical decisions with business goals, and helping internal teams work more effectively together over time.

Collaboration style is worth watching closely, particularly under real pressure. Some teams become defensive the moment they’re challenged. Others simply disappear into process instead of engaging directly. Strong partners, however, stay transparent, pragmatic, and solutions-focused throughout. They explain trade-offs clearly, challenge unrealistic assumptions when they see them, and stay honest about complexity and risk rather than avoiding difficult conversations.

A successful launch matters, of course. A platform that continues evolving cleanly years later matters considerably more. That outcome only happens when an agency is genuinely willing to push back, rather than simply agreeing to everything you ask for.

If you’re looking for a WordPress agency currently, we’ve got just the guide for you. Download The Definitive Guide to Choosing an Enterprise WordPress Agency, which comes complete with an evaluation scorecard to help you assess agencies against the criteria we’ve covered in this article.

How These Four Pillars Help You Evaluate an Enterprise WordPress Agency

None of these four pillars function well in isolation from one another. For instance, a technically excellent platform can still fail badly if delivery maturity is weak. Nobody clearly owns the decisions the team makes along the way. Likewise, strong governance means very little if the underlying architecture simply can’t scale to meet real demand. In short, the four pillars reinforce one another. That’s exactly why evaluating just one of them, usually technical capability since it’s the easiest to demo, tends to leave real risk completely unexamined.

PillarWhat good looks likeWhat a vague answer sounds like
Technical capabilityClear trade-offs and plain-language explanations of architecture decisions“We use best practices” with no specifics offered
Delivery maturityA documented discovery process and clear escalation paths“We’re very collaborative” with no real process detail
Security & governanceGovernance built into the design from day oneAccessibility and security framed as a late-stage QA task
Strategic alignmentA willingness to challenge timelines and underlying assumptionsAgreeing to every requirement without any pushback at all

Resources to Help You Evaluate an Enterprise WordPress Agency Further

If you’re actively evaluating agencies right now, a few other resources pair well with everything covered above:

The Bottom Line on How to Evaluate an Enterprise WordPress Agency

A visually impressive site means very little if the platform is hard to scale, govern, or maintain a year from now, regardless of how strong the original pitch was. Ultimately, learning how to evaluate an enterprise WordPress agency means weighing all four pillars together. Don’t rely on whichever single pillar happens to demo the most impressively during procurement.

Frequently Asked Questions

The best approach weighs four areas together rather than any single one in isolation. Technical capability covers whether they can explain architecture decisions clearly. Delivery maturity covers whether they run real discovery and QA processes. Security and governance covers whether they build compliance in from day one. Strategic alignment covers whether they’ll challenge unrealistic timelines rather than simply agreeing to them.

Delivery maturity refers to an agency’s process discipline. That includes how they run discovery, manage stakeholders, document decisions, and handle QA and releases throughout a project. It matters just as much as technical skill, since most enterprise project failures stem from weak process rather than any single bad technical decision.

Ask how they approach architecture and extensibility, and what their deployment and testing workflows actually look like in practice. Also ask how they manage technical debt as a platform grows over time. Strong agencies tend to answer with specifics and clear trade-offs. Weaker ones often speak in generalities or lean heavily on jargon instead.

The post How to Evaluate an Enterprise WordPress Agency: The 4 Key Pillars appeared first on Human Made.

Questions To Ask When Choosing A WordPress Agency

3 September 2026 at 15:49

Choosing the wrong WordPress agency rarely looks like a mistake at the time. It looks like a great pitch, a polished proposal, and a shortlist of impressive client logos. The problems don’t surface until months into delivery — and by then, switching agencies costs time, money, and momentum.

The right questions can surface most of this risk before you sign anything. Weak agencies tend to answer vaguely or pivot back to generic features and deliverables. Strong ones answer with specifics, trade-offs, and real examples, because they’ve solved these problems before.

Below, we break down the questions to ask when choosing a WordPress agency, organized by what each one actually reveals. If you want the full framework behind these questions, including a ready-to-use scorecard, check out our Definitive Guide to Choosing an Enterprise WordPress Agency.

Why the Right Questions Matter More Than the Right Proposal

Most enterprise WordPress agencies look nearly identical on paper. Anyone can polish a set of case studies, a service list, and a pricing model. What’s much harder to fake is a confident, specific answer to a question the agency didn’t expect.

That’s why we built this list of questions to ask when choosing a WordPress agency around real delivery experience rather than generic hiring advice. Each question tests whether an agency has actually lived through the problem you’re asking about, or whether they’re guessing. For a deeper look at how to weigh the answers, our post on the true cost of choosing the wrong agency explains what happens when organizations skip this step.

Questions About Technical Capability

How do you handle WordPress core and plugin updates at scale?

This question makes a good early test of technical maturity. A vague answer (“we keep things updated”) suggests the agency has no real process. A strong answer covers staging environments, pre-deployment testing, and how updates roll out across multiple sites or environments without breaking production.

What does your deployment workflow actually look like?

Ask the agency to walk you through their workflow step by step. Agencies with mature engineering practices describe this clearly and confidently, from code review through to release. If they struggle to explain it, they probably don’t run a consistent one.

How do you manage accessibility over time, not just at launch?

Many agencies treat accessibility as a late-stage QA checkbox, and that approach tends to break down within months of launch. Strong agencies build accessibility into their design systems and development workflows from day one, and they can describe exactly how they maintain it as the platform evolves.

How do you approach integrations, and what happens when one fails?

Every enterprise platform connects to other systems — CRM, DAM, analytics, marketing automation. Ask how the agency handles failure states, documents dependencies, and keeps integrations maintainable as requirements change. Saying “yes, we can integrate that” is easy. Explaining how they’ll keep it working two years from now takes real experience.

Questions That Reveal WordPress Agency Evaluation Red Flags

How do you approach governance across large editorial teams?

This question separates agencies who’ve genuinely worked at enterprise scale from those who haven’t. Governance at scale means structured permissions, clear escalation paths, and editorial workflows that hold up as teams and content volumes grow. Our breakdown of WordPress agency red flags and green flags covers this pattern in more detail.

What happens when requirements shift significantly mid-project?

Requirements always change. What matters is whether the agency runs a repeatable process for handling it, or treats every change as a renegotiation. Listen for how they discuss trade-offs and re-scoping, not just how accommodating they sound in the room.

Who owns what — delivery, technical direction, and continuity?

Ask directly: who leads delivery, who owns technical decisions, and what happens if a key team member leaves mid-project? Vague answers here often signal unclear accountability once you’re actually working together.

Questions About Long-Term Partnership and Support

How do you reduce technical debt during long-running engagements?

If an agency has never had to answer this question, they’ve probably never run a long engagement. Technical debt accumulates on every platform — the real question is whether the agency actively manages it or lets it compound.

What’s included in the retainer, and how do you manage priorities?

Post-launch support models vary enormously. Some agencies offer proactive, strategic partnerships. Others run reactive ticketing systems that create bottlenecks the moment something urgent comes up. Ask specifically what the retainer covers, how they set priorities, and what SLAs apply.

What operational issues tend to emerge after launch?

This question works as a good gut check. Agencies with real enterprise experience usually answer readily and specifically, because they’ve watched the same patterns repeat across clients. If an agency has nothing to say here, they may not have supported a platform long enough to know.

What a Weak Answer Sounds Like (vs. a Strong One)

Weak answers share a pattern: they stay vague, pivot back to generic features and deliverables, or dodge the specifics of the question entirely.

Strong answers share a different pattern: they include real trade-offs, concrete examples, and an honest acknowledgment of risk. A strong agency won’t shy away from saying “here’s where this gets difficult,” because they’ve already solved that problem before, more than once.

If you take away one thing from this list, take away this: the specificity of the answer usually matters more than the answer itself.

FAQ: Questions to Ask When Choosing a WordPress Agency

What’s the most important question to ask a WordPress agency?
There’s no single most important question, but the strongest signal usually comes from asking what happens after launch — support models, technical debt, and how the agency handles changing requirements. These answers reveal whether an agency thinks long-term or just wants to get you to go-live.

How do I know if a WordPress agency is enterprise-ready?
Look for specific, confident answers about governance, accessibility, integrations, and post-launch support, not just a portfolio of recognizable client logos. Enterprise-ready agencies can explain their processes in detail because they’ve repeated them across multiple large-scale engagements.

What are red flags when hiring a WordPress agency?
Common red flags include agreeing to every requirement without pushback, giving vague or generic answers to technical questions, offering little visibility into QA or release processes, and focusing purely on launch with no discussion of what comes after.

Should I ask these questions during an RFP or in a follow-up conversation?
Ask them in both places, ideally. A whole team can polish a written RFP response. A live conversation, where you can ask follow-up questions and probe deeper, often reveals the real differences between agencies more clearly.

Choosing With Confidence

Asking sharper questions earlier remains one of the simplest ways to avoid an expensive agency mistake later. It costs nothing, and it tends to reveal far more than any proposal will.

For a deeper framework — including a full evaluation scorecard — take a look at our Definitive Guide to Choosing an Enterprise WordPress Agency.

The post Questions To Ask When Choosing A WordPress Agency appeared first on Human Made.

The Total Cost Of Choosing The Wrong Enterprise WordPress Agency

By: Lorna Lim
2 September 2026 at 13:02

The cost of choosing the wrong WordPress agency rarely shows up at launch. It surfaces quietly, months or years later. A platform that once felt like a win starts costing more with every release. The financial cost of a bad agency choice is the easy part to calculate — it’s on the invoice. The total cost of ownership of a WordPress platform is harder to see. It’s the number that actually determines whether your organisation can keep moving at speed – and procurement almost never sees it.

The cost of choosing the wrong WordPress agency rarely lands where you’d expect it to. Here’s where that cost shows up, and why it compounds.

The invoice isn’t where the cost lives

When an enterprise WordPress project goes wrong, the instinct is to look at the budget line. Did it run over? Did the retainer balloon? Did you end up paying for a second agency to fix the first one’s work? Those numbers matter, but they’re not the real damage.

The real damage is behavioural. Once a platform becomes hard to maintain, the organisation adapts around it rather than the other way round. Editorial teams start avoiding certain templates because they’re fragile. Marketing quietly delays campaigns because releases feel risky. Engineers spend their sprints managing regressions instead of building anything new. None of that appears on an invoice. All of it is cost. It’s part of what makes the hidden cost of WordPress migration and development so easy to underestimate at the outset.

Why do Enterprise WordPress projects fail after launch, not at launch?

A rough timeline of where enterprise WordPress project failure actually surfaces:

At launch: Everything looks fine. The site is live, the demo works, the stakeholders are happy. This is the moment procurement teams use to judge success. It’s also the least informative moment in the platform’s lifespan.

Around month six: The first real cracks appear. A content model that didn’t anticipate a new use case. A plugin conflict nobody caught. An integration that sales quietly approved but nobody stress-tested. Small, individually forgivable.

By year two: The cracks have merged into a pattern. Releases take longer than they should. Every new feature request comes with a caveat about what it’ll break. The platform technically works, but nobody trusts it to change gracefully. By now, replacing the agency (or the platform) feels far more disruptive than it would have eighteen months earlier.

That lag is precisely why the cost of choosing the wrong WordPress agency is so easy to underestimate. The bill doesn’t arrive until you’re already locked in. If you’re trying to put a number on how much a failed WordPress project actually costs, look at this delayed timeline. It matters more than the original invoice.

Why “It launched successfully” is a weak signal of vendor selection risk

Enterprise buyers naturally weight the launch heavily when they judge an agency. It’s the most visible milestone in the relationship. It’s also, often, the milestone procurement scores most heavily. That’s part of why RFPs can miss the signals that actually predict long-term WordPress agency vendor selection risk.

But a successful launch tells you almost nothing about whether the agency built the platform to last. Sustainable architecture doesn’t demo well. Governance processes don’t show up in a highlight reel. You see the quality of an agency’s decision-making far more clearly under pressure than on day one. A traffic spike. A mid-project scope change. A new integration nobody planned for. That’s when the platform’s real behaviour shows.

This is also why cost and risk are so tightly linked. The platforms that launch cheapest tend to be the ones where a lot of that pressure-testing simply didn’t happen.

Is the cheapest WordPress agency worth It? The false economy of the lowest bid

Lower-cost proposals are attractive for an obvious reason. Enterprise teams scrutinise budgets, and a smaller number is easier to defend internally. But agencies rarely cut margin evenly across a project. What tends to shrink first is exactly the work that doesn’t show up in a demo. That includes discovery time, QA depth, and documentation. It also includes accessibility work and the architectural thinking that makes a platform easy to extend later. This is the cheap WordPress agency risk in practice — the corners you can’t see get cut first.

None of that absence is visible at handover. It becomes visible the first time the organisation asks the platform to do something the agency never built it for. By then, you’ve usually spent the original saving several times over — in slower releases, firefighting, and remedial work.

This is the core problem with judging an enterprise WordPress agency on launch price alone. You’re pricing the one moment that tells you the least. You’re ignoring the years that will tell you the most. It’s also the honest answer to whether the cheapest WordPress agency is worth it. Rarely — once you account for what happens after launch.

What does total cost of ownership mean for a WordPress platform?

Total cost of ownership for a WordPress platform isn’t just the build fee plus hosting and support retainers. It’s the build cost, plus every hour spent working around fragile templates. Add every delayed campaign, and every remedial project needed to fix architecture that couldn’t scale. Measured this way, the cheapest agency at procurement is frequently the most expensive one three years in.

Judge the decision on its lifespan, not its launch

The organisations that get this right tend to ask a different question during procurement. Instead of asking what this will cost to build, they ask a different question. What will it cost to operate, change, and grow over the next three years? That single reframe changes almost everything about how you evaluate a partner. A platform that’s slightly more expensive to build but genuinely easy to evolve will almost always win out financially. It beats a platform that was cheap to launch and expensive to live with.

A successful launch is a nice moment. It isn’t the test. The real test of whether you chose well is simple. Does the platform still feel adaptable and stable? Is it still worth investing in, two or three years after everyone’s stopped talking about the launch? That’s long after the true cost of choosing the wrong WordPress agency would otherwise have made itself known.

If you’re currently evaluating enterprise WordPress partners, run that three-year lens over every proposal before price becomes the deciding factor. Our Definitive Guide to Choosing an Enterprise WordPress Agency covers the full evaluation process.

The post The Total Cost Of Choosing The Wrong Enterprise WordPress Agency appeared first on Human Made.

#234 – K. Adam White on Migrating to Blocks With Artisanal Care and Enterprise Efficiency

23 September 2026 at 12:53
Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, migrating to blocks at an enterprise level and what’s involved in moving from a different CMS into WordPress.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today, we have K. Adam White, or K. Adam for short.  K. Adam is the principal engineer at Human Made, an enterprise WordPress consultancy. He’s been involved with WordPress for almost 20 years, attending his first WordCamp in Boston back in 2011, and has contributed to WordPress Core and the broader open source ecosystem. Human Made is known for delivering complex projects, think high stakes, no room for mistakes? From global brands moving to WordPress.

This time around,  K. Adam delivered a presentation at WordCamp US focused on a crucial topic for anyone modernising their site, migrating to blocks. Human Made has been all in on the block editor since the Gutenberg plugin days, and the team now specialises in large scale migrations from other content management systems like Sitecore, as well as from other WordPress page builders.

Our conversation focused on the technical and editorial challenges of moving tens, or hundreds, of thousands of posts into the world of blocks and patterns. We talked about the need to combine artisanal care, attention to detail in design, layout, and brand, with industrial scale. The ability to automate, audit and validate mass migrations without losing visual fidelity.

We also discussed the use of patterns as a foundation for development, integrating custom and Core blocks, and leveraging new tools, including AI powered agents and open source plugins like Human Made’s, own rehydrator, to streamline migration workflows.

We also touched upon how clients are onboarded. The process of auditing legacy content. Strategies for training editorial teams on the block editor. And there’s a frank reflection on gaps in WordPress, like granular content permissions.

If you are contemplating a move to the block editor, wrestling with a massive content migration, or curious about what happens when enterprise complexity meets the flexibility of WordPress, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you  K. Adam White.

I am joined on the podcast by K. Adam White. Hello, K. Adam.

[00:03:41] K. Adam White: Hello. It’s good to be here.

[00:03:42] Nathan Wrigley: Yeah. Thank you for joining us. You have an interesting name. Just go on, I know it’s totally off piste, but tell us about your name.

[00:03:49] K. Adam White: Sure. It’s a first initial K, and the middle name Adam that got conjoined in college and I quite like it. So I think in a sphere, and a particular niche in WordPress with so many Adams of so many different colours, then K. Adam is a little bit more me.

[00:04:04] Nathan Wrigley: Yeah, nice. So we’re in the corridor, so forgive any noise that you hear on this podcast episode. We can’t avoid it. We’re in the corridor at  WordCamp US, and you have done, some presentation work this time around. Do you want to just tell us, I mean I presume it’s happened because we’re at the very closing stages of the conference. How did it go?

[00:04:21] K. Adam White: It went, as far as I can tell, quite well. My session was early yesterday, right after the morning keynotes in that early slot where everyone’s coffee has kicked in, and the fatigue of the conference hasn’t quite set in yet.

So I had a great audience and the talk I thing went quite well. I’ve had a number of different conversations off the back of it on various different topics that I covered. So the breadth of those discussions has been really exciting for me.

[00:04:44] Nathan Wrigley: So that is going to be the meat and the bones of what we’re going to talk about today. But first, if you don’t mind, let’s talk a little bit about you and what you do and where you work, just so that we can paint your credentials if you like.

So tell us about your job, how long you’ve been in the WordPress space? Who do you work for? Et cetera.

[00:04:59] K. Adam White: Yeah. My job is principal engineer at Human Made. We’re a WordPress enterprise consultancy, and I have been there nine years. I’ve been in the WordPress community quite a lot longer than that. My first WordCamp was WordCamp Boston 2011, which is a mind boggling 15 years ago now. And before that, I had been using WordPress personally since 2007. So we’re coming up on 20 years of involvement, at least as a user. And then, became a contributor in the early 2010s around 2013, I think my first commit landed.

[00:05:25] Nathan Wrigley: Yeah, nice and Human Made, if you haven’t heard, we’ll put the links into the show notes, anything that K. Adam mentions today, we will put us a link on the WP Tavern podcast episode website, so you can click through to it. But go and check out Human Made, definitely one of the big hitters. I think it’s fair to say in the WordPress space.

[00:05:40] K. Adam White: It’s very kind of you to say so.

[00:05:42] Nathan Wrigley: You did your presentation and it was entitled, Migrating to Blocks. I’m going to intuit from that, that Human Made is all in on the block editor. You’re not using some sort of other proprietary platform. Would that be the case?

[00:05:55] K. Adam White: That would be the case. We were very early adopters of Gutenberg back in its plugin days. We were doing work before it was merged for building out some early block sites, testing out what we could do. Learning how to build and change our theme development processes to move in a more block oriented direction, and then follow that directly into the Full Site Editor world.

And it’s been a great ride. We do work with other page builders and other blocks, platforms and frameworks. We do tend to, as a company, work on projects that have some sort of particular technical complexity that made someone come to us rather than a different agency.

That does mean that we are broadly specialised in WordPress as a platform, including many of those page builders. We’ve worked with Elementor, we’ve worked with Divi, Beaver Builder, but we as a company will always advocate for the block editor and the site editor. And we have our own processes oriented more and more towards delivery with that framework in mind.

I think that the thing that is bringing some of the companies that we help to migrate to WordPress into this ecosystem is the flexibility and the quality of the editorial experience. And personally, my opinion is that Gutenberg does that leaps and bounds better than any of our other page builders that don’t have that native integration into the platform.

[00:07:09] Nathan Wrigley: So if a client comes to you and they are agnostic as to what you are going to build with, your default posture would be we are going to use the block editor.

[00:07:16] K. Adam White: Absolutely default.

[00:07:17] Nathan Wrigley: Okay. And do you have to do any level of persuasion anymore? I’m guessing if we were to rewind the clock, let’s go to 2017, soon after Gutenberg started to become more widely available. I imagine there was quite a bit of explaining to do. Do you still have to do any of that? Or is it a case now that the enterprise people understand what’s going on, and there’s less of a back and forth about whether they should use blocks and patterns and whatever else?

[00:07:41] K. Adam White: If we are building from scratch, we haven’t found there is any reluctance. Particularly if people are coming from a different content management system, particularly a different enterprise content management system. The editor is so compelling, that there’s never any objection to using it. They might ask, should we use this or some other thing I’ve heard of? And we can say, the block editor is built in. We feel that it’s the most robust and future proof platform that you can choose. So we would recommend going that route rather than adding in another plugin, however good they are.

But we do still, nonetheless, have some projects where they are already on a page builder, and they might have invested a lot of training. We might have an entire business school worth of people that are very comfortable with whatever their existing system is, whether that’s Beaver Builder or something else, et cetera, Elementor.

And I think that it’s very important for us to remember what our remit is when we come into a project. That, doesn’t always involve helping them change everything to match what we see as the future. I think that’s a responsibility of the client to understand where they are in conjunction with where the WordPress roadmap is, and make their own decisions about what tools are right for them.

So, for existing projects, we’ll work with what’s right for the clients editorial team, but if we have to make a recommendation, it will always be the block editor.

[00:08:56] Nathan Wrigley: Okay. Yeah, good to know. At place in the market where you are, I’m presuming there’s very little room for error. When you build something, it’s got to work out of the box, on day one. You’ve presumably got stakeholders who’ve got editorial teams, and they’re fairly, we’re, dealing with large corporations that can’t afford for there to be mistakes.

So that kind of leads us to the nature of your presentation, which was called, and again, links will be in the show notes on wptavern.com. Migrating to Blocks with Artisanal Care and Industrial Scale. And I’m actually just going to read the first paragraph because it summarises what we’re going to talk about perfectly. It’s fairly long, but I’ll go through it all.

Whether we’re modernising an old personal blog or migrating hundreds of thousands of existing posts from another CMS. Using WordPress in 2026 means converting our contents to blocks. The convert to blocks button in the editor works well enough for one post. But if we have dozens or hundreds, what can we do to make the process less manual and more powerful? How can we integrate a site’s content directly into full block patterns without losing the columns and structure it had before? And then it goes on to mention, a particular build, I presume, where you were leaving one CMS coming into WordPress.

Just lay out some of the fun, interesting problems that you have to overcome when you’re moving from an entirely different CMS into WordPress, because I guess it’s more complicated than, “Look, there’s a bunch of paragraphs and images. Let’s just drag those over and hope for the best.” Tell us what the problem before you is.

[00:10:22] K. Adam White: That’s a great question. It’s actually remarkable how close you can get to satisfaction with just moving paragraphs and images over and hoping for the best. But there is a big gap in terms of visual fidelity.

The editor in a theme that we’ve built for a client will be configured with patterns and templates and all of the block variations that they need to be able to very quickly sketch out a page. If they are starting from scratch, a client with a fully site editing enabled theme can drop a hero pattern on the page, set in the media they need. Change any font sizes within the pallet of what’s available with their brand guidelines encoded in the theme.json. It’s very easy for them to build out and write content fresh.

But if you have, again, hundreds of thousands of posts, even if you’ve built all those patterns, the heading and paragraph and image only approach doesn’t cut it, because then there would be a tremendously backbreaking amount of work, adding group blocks, adding background colours, et cetera.

That’s usually data that is available in one form or the other in the current system. If we’re migrating without a design change, we will have, whether it’s the layout database in Sitecore or a metadata in a different WordPress block editor that we’re migrating from. Or whatever the equivalent is in our source. We want to preserve the layout of the page and the styling elements. So making sure that headings get the right text treatment, that anything that’s italicised comes over. All of the nuances there, particularly around background colours, images, et cetera. That’s the piece that we’ve been over the past year, looking at how we can improve our process when we’re building a new site, but bringing content over from an old.

Within that context, my talk covered two broad areas. The specific tail end of the talk was about how we can actually use the theme patterns that already exist in the theme directory, and use those to inject particular pieces of source data. So if you have a pattern for a hero element, and you know from your source data what the image URL is supposed to be, what the title is supposed to be. We can use the HTML directly from the pattern file, and do lightweight search replaces within that using either direct PHP string replacements or a tool that we’ve written, that I shared a link to called rehydrator, which is a very early stage experiment, that we’ve got out on GitHub.

And we can use that to put the content into the structure that it’s going to need to have for it to be fully, visually correct. So rather than just reducing and throwing away anything that isn’t a heading or a paragraph, we’re taking the framework from the theme pattern that’s been built. And then we’re writing a migrator that takes data and puts it into that HTML structure, and saves that into the post content. So that when an editor opens up a page, it loads correctly in the editor without block validation errors and it looks right on the front end.

[00:13:15] Nathan Wrigley: Okay. There’s a lot of depth in that, isn’t there? We’ll come back to that in a moment.

I’m curious about process of how you, persuade clients that you are going to be able to carry this work out successfully. So how does that actually work? You obviously look at their existing content, you have a discussion about what the new design is going to look like, and then do you build out some kind of templates or patterns or what have you, so that you can then pull in a proportion of the content, maybe, I don’t know, 10 or a hundred or 5,000 or whatever it may be, pieces of content. Check that that’s all right. Show it to the client. How does that workflow go to build up their confidence that what you are going to do when you finally click the button is actually going to succeed?

[00:13:50] K. Adam White: The way that we’ve been approaching that, I think particularly, over the past six months, I should caveat first that this process has changed so much. Because the tools we have available with AI agents have been evolving in leaps and bounds alongside this particular migration process, which started in January.

So in this case, we started out by building patterns that we could put content for one test post, from the existing site manually. Bringing the contents over, copying and pasting headings, et cetera. And using that to create the patterns that we could show to the client to say, does this look correct? Does this structure mirror what you’re expecting? Is this what you expect an author to have available within the post editor?

And then you know, which pieces belong in the template, which pieces are managed at the site editor level? We’ve done a lot of that ahead of starting the actual migration.

Now that the migration is in progress, any subsequent pieces we’re developing in tandem, we’re saying, okay, we have a press release. That press release, we have audited the incoming data, and we have determined that there are four different layouts for press releases. And this one is used the most and it has these elements. This one is used less, but it has images, et cetera.

And we can build the template for that post type, and at the same time write the migrator for identifying the content nodes, and the source data and bringing that information over into the new patterns.

So we have the patterns that we can show, okay, if you’re building something from scratch, this is what that looks like in the editor. But then at the same time, we can run the migrator over, in most cases, all of the relevant type of data and say, and here is a list of pages to validate.

So what we’ve been doing is bringing that to our stakeholder, and allowing them to do spot checks, so that they can look through and validate that there are all of the required elements on the test pages. Things like, “oh, alright, we don’t have a mapper yet for video embeds. So videos are missing,” and that’s usually going to be an all or nothing thing. We’ve found very few cases where we end up with one or two errors on a specific post basis that aren’t related to support for a complete type of output pattern.

[00:15:55] Nathan Wrigley: Is there a sort of fault tolerance there? So obviously in the case of this particular migration, tens of thousands of posts, I guess there’s never going to be a moment where you can be a hundred percent confident apart from reading the 10,000 posts that you’ve done everything correctly. Is there a, we’ll do 10 to begin with, then we’ll go up to a hundred, then we’ll go up to a thousand.

What, is the sort of tolerance that you present to the client? I’m just imagining that just lurking in post 9,999 is just some weird thing that was allowable in the CMS but never got used before or since, and that piece of content got missed. I don’t know what’s allowable in that scenario. So is there any level of tolerance for fault?

[00:16:32] K. Adam White: The major advance that we’ve made with migrations as a broad structure this year is a much better understanding of those edge cases. And the way that we’ve done that is by leveraging Claude and various other tools to do cross site audits to make sure that we have a full picture of the source data.

So we are able to feed in whatever export files we get from our source site. In this case we’re working from Sitecore, which is an enterprise CMS, which has two database structure. There’s actually a database with a content tree, and then another database that contains layout information. And a page is rendered by switching back and forth between those and assembling the final output.

We were able to get exports of the relevant content from both of those, from the developer of the current site. And we fed those and a whole bunch of documents from the product owner into a ongoing conversation with Claude. And we’re able to use that to build some actually node.js scripts that would take the files we’d gotten from the Sitecore devs, and build a local database in SQLite that each developer on the team was able to run locally. And we can query against that to find those edge cases.

So in a combination of writing our own manual queries, or having a chat conversation prompt for finding individual things, and then it will run a number of queries and report back to us. We’re able to identify very quickly, oh, there’s only one press release that has images, that’s interesting. But there are 17 that have a FAQ accordion.

So that type of auditing has become trivial, and it’s mind boggling how much faster that’s allowed us to move in terms of understanding the data that’s there, and building out a mapping of how we’ll migrate through the different types of content.

We don’t tend to start with only 10 pages in a post type because it’s relatively cheap to run the migrator over a thousand instead of 10. And that gives you a lot more content for both various people on the client team, but then also agentic tools to click through and do a little bit of spot check validation.

What we tend to do is to migrate content type by content type, and we’ll prioritise those based on what we see as the balance between scale and complexity.

[00:18:39] Nathan Wrigley: Do you leverage Core blocks wherever possible, or do you bring bespoke Human Made blocks where that’s necessary? Or can you basically bind everything in this particular build to a Core block?

[00:18:51] K. Adam White: Most of the time we will start with Core blocks and get as far as we can with them. This is a change from how we used to do it. Our early days, we had a lot of rapid iteration in the markup that Core blocks were using. In some cases, there was a lot of evolution in how the controls for them were set up.

[00:19:07] Nathan Wrigley: It was brutal.

[00:19:09] K. Adam White: It was brutal. But that pace of change for the main building blocks of a site has slowed down tremendously, and I think it’s a very stable foundation. So we will be pattern first in our development. We will start by working, doing a lot of in-editor prototyping actually, to build out layouts and patterns for each individual unit of content, each individual sort of component group in the source site. And, it will only be when we run into something like a carousel or a modal that we might reach for a off the shelf, third party option that’s not in Core, or bring our own solution to the table.

[00:19:45] Nathan Wrigley: So do you take, when you said pattern there, is a pattern a sub component of a, let’s say post for want of a better word? Or is it that the pattern is the entire post with bits injected into it? So paragraphs, headings, videos, whatever it may be? Like I said, at the beginning, or are you building up the entire post from various different patterns? Here’s a video pattern and here’s a, I don’t know, a paragraph pattern with a heading? Or a background image or whatever it may be.

[00:20:12] K. Adam White: Patterns tends to be at number of different levels. We might have individual patterns for a particular treatment of headline for example. But we also will have a pattern for a hero section. We’ll have a pattern for a hero section plus the bio below that, that we can use to populate a template in the site editor.

We build patterns at multiple levels of granularity, and we have a leaf to trunk system where we’ll make sure that we have renderings, whether they’re Core blocks with either default styling or one or two block variations, or individual patterns for things where we need to compose one or two blocks together. We’ll make sure that we have all of those leaf node pieces of content, all of our paragraphs, all of our inline images. And then we’ll build patterns for those higher level groups, the full width backgrounds with coloration and a particular headline treatment.

We build out those patterns at all of those different levels because it’s nice to have the granularity when we’re writing our migrators, and patterns can reference each other. So you can have an accordion pattern, which includes two references to an accordion item pattern, and you can have all of those little bits of HTML be discreet PHP files in your WordPress theme. So it makes it very simple to pull up in your editor only the code that you need to edit for a particular unit and know how that’s going to be scoped.

[00:21:26] Nathan Wrigley: This is going to sound like such a peculiar question, but it genuinely, from my point of view, this sounds like really interesting and curious work. It sounds, like there’s a lot to get your teeth into. You’re pushing the boundaries a little bit, but also you’ve got the scope of WordPress, which kind of makes it slightly easier.

I’m basically just making the comment that I think I would enjoy doing the work that you are doing. I don’t know if that, yeah, there really a question there.

[00:21:47] K. Adam White: Unfortunately, we’re doing less and less of that work, and Claude’s doing more and more of it. It’s been actually very efficient because this is such a core central construct in the WordPress block editor. There’s a lot of good documentation about it and agentic tools are quite good at helping to build pattern markup.

So, what we’ve been doing is bringing our human eyes onto that, doing all of our spot checks, making sure that things are kept as simple as possible. Because I think we’re all familiar with how verbose and overly complicated output can be from some tools. But then it is also something that I really wish more people were talking about and doing. Brian Coords earlier today in his talk, mentioned that pattern driven development really he sees as something that more and more of the WordPress community should be trying out. Because there are so many things that we used to build custom blocks for, that just strictly aren’t necessary anymore. And we can get so far by composing what we get from the lego kit of WordPress out of the box.

[00:22:40] Nathan Wrigley: Yeah, I feel like if we went back to 2015 and began Gutenberg again, I feel going patterns first would actually be a nicer approach, certainly a more straightforward approach. I know that there’s, ways to overcome that, but I always drop patterns in, never blocks, and then I’m always interacting with the blocks within the pattern. But it’s patterns first for me all the time. Just because I like the fact that I’m dropping in multiple bits of content that are pre-configured and pre-made and pre, I’ve fiddled with the CSS and made it just how I like it. And I just click the button once and there it is, and I can just rinse and repeat and it’s really straightforward.

[00:23:12] K. Adam White: I would agree, and over the past two to five releases of WordPress, we’ve also had such powerful additional tools added to the pattern toolkit. For example, Partially Synced Patterns. Was a major topic that I shared in my talk. Being able to have a reusable pattern and then make the content editable on a post by post basis makes it very seamless for a non-technical editor to go in, and not have access out of the box to stylistic controls that would make something drift from the brand’s guidelines that they’re trying to follow, but still be able to customise link targets, CTA, text, all of the descriptive and image elements.

[00:23:47] Nathan Wrigley: You are in the weeds of WordPress, and I’m in the weeds of WordPress all the time, but I still feel those tools are widely, not misunderstood, that’s the wrong, just there’s a void. Nobody even knows they’re there. There’s just tonnes of tooling inside the block editor that people simply don’t know about, because the UI and the UX is still a bit funky. You’ve got to go to various different places, and it’s easy to go down the wrong route.

Do you know what I mean? There’s a bunch of tools inside a WordPress that if you only had a few hours with somebody over your shoulder pointing out, “okay, click on that, look at that menu that does this thing.” It’s a shame in a way that’s the case. But I do feel there’s a lot of unexplored potential in every WordPress website that presumably you are leveraging. But I guess just because you’re in the weeds of it.

[00:24:30] K. Adam White: Wherever possible, we have the privilege of having a lot of history with the CMS. Human Made was founded in 2010 and has always had a strong open source posture. We’ve contributed to Core, we’ve put plugins out there in the ecosystem that are used by a number of other agencies. We’ve found the best of what our frenemy competitors use, and been able to adopt those into our own processes.

And the benefits of understanding all of the different types of block that you can use tremendously outweigh any time sink that it takes to learn them. I hope that, from my talk, people will now know that in 7.0, we added PHP only blocks, where you can have the attributes auto registered so that you get, even as a non JavaScript developer, a interface in the editor that someone can open up and go in and change values in the sidebar.

I hope that more people learn about Partially Synced Patterns. I hope more people learn about all of the different types of block that we have available, and find ways to integrate those into their own toolkits. Because playing with the grain of WordPress and using the Block Editor for all it’s worth, are how we untap the most value for our clients.

[00:25:34] Nathan Wrigley: Yeah, there is certainly an awful lot of power, and like I said, I just think some of it gets missed.

How much after you’ve done the migration, how much time do you have to spend with the clients? I have this impression that the Gutenberg editor is pretty straightforward, muscle memory for me essentially. Hours of playing in it. I know where all the bits and pieces are.

But I would also recognise that if I was to show it to somebody who’d never played with WordPress and was coming from, in this case Sitecore, how overwhelming is it? And do you take steps to make it less overwhelming by minimising what’s available in the interface, or just disabling options? What do you do in that regard?

[00:26:08] K. Adam White: No matter how much flexibility our clients want, it’s usually valuable to disable some options. I can’t remember a site we’ve shipped recently for any large website where we left the custom colour picker in, for example. You want to do a better job of limiting what people can use, so that we have confidence that the output, no matter how design savvy or not someone is, is going to be consistent with the rest of the site.

My colleague, Joeleen Kennedy, gave a talk a couple years ago at the first  WordCamp US Showcase Day back in 2024, about work we had done customising the editor for that type of simplicity. And in particular things that we can do around colour palette selection. Ways that we can hide the styling controls for certain blocks through having them embedded in a pattern.

It’s interesting to see that in WordPress recently, if you are editing content that has been marked as having come from a pattern in a post, you can edit all of the text, you can edit all of the images and link targets, but you actually have to hit edit pattern in the sidebar in some cases, depending on how the post is set up, to get into the details within the post that allow all of those other controls to be visible.

That divide took a tiny bit of adjustment for people on our client teams, but the separation has helped them stay focused on the content, and worry less about the overwhelming, combinatorial set of styling possibilities that their blocks have.

[00:27:29] Nathan Wrigley: Do you think that the necessary tools are already built into WordPress to do the kind of work that you are doing? Or is there some missing piece that would make it easier for somebody who doesn’t have the deep pockets that presumably Human Made would require, to do that kind of work. Is the default tooling usually okay to migrate things or have you had to build loads of bespoke tooling?

So in terms of if I was to approach a WordPress website and try to migrate from Sitecore over to WordPress, is this something that you absolutely need a team to do, or would you be able to get some simulation of this with Core WordPress?

[00:28:04] K. Adam White: If you had access to the exports of data from a Sitecore website, and you had a core vanilla WordPress install. And you had a LLM tool of some sort, I think that you could do a lot to get close to what you want. The LLM piece, I think enables this to be done by more people without having to be completely familiar with all of the internal nuances of WordPress. You need to direct it to the architectural pattern that you want, but we have found that it speaks Gutenberg pretty well.

[00:28:32] Nathan Wrigley: What was the name of the tool that you said you’d custom and built?

[00:28:34] K. Adam White: We had built a plugin called rehydrator.

[00:28:36] Nathan Wrigley: Okay, rehydrator, yeah.

[00:28:37] K. Adam White: rehydrator is the tool that we use to take a pattern in the theme and then use that pattern as the template when we’re bringing content over to make sure that we keep all of the styling theme side, and that our migration script doesn’t duplicate the markup specifically.

[00:28:51] Nathan Wrigley: What’s Human Made’s approach to the WordPress project in that regard? You said it was a plugin. Does that mean it’s a wordpress.org repository plugin, or is it one that you have on your own, I don’t know, GitHub repository or whatever it may be.

[00:29:01] K. Adam White: We have some things in the .org repository. In this case, that particular plugin is only on GitHub. A number of ones that we build are only on GitHub, because we’re building them for a very transient in time period of a site.

You don’t need a migration tool to be part of your site long term, it’s not something you’re going to be leaving active, and updating month over month when there is a site running. It’s something that you bring in for the purpose of populating the data. And then you can remove that.

And in that regard, for this particular one, at the moment it’s partly because it’s quite young, and it’s also because we don’t see it as being general purpose. So that plugin specifically is on GitHub and publicly available through Composer, but not on the plugin directory.

In other situations, we’ve gone the opposite direction, and anything that we see as being a ongoing value to a site as it’s running, we do try to move those over as we can.

[00:29:52] Nathan Wrigley: Given that you are on the sort of engineering side of Human Made, I don’t know if this question will land, but we seem to be in this interesting period where there’s a lot of chatter, AI kind of fits into the equation a little bit, but there’s a lot of chatter about the, market share of WordPress and whether or not WordPress as a tool will continue with the same numbers and clout and market share and all of those kind of things.

Do you notice at the enterprise level that there’s been any kind of change in a southerly direction? Maybe there’s been a direct change in a northerly direction. What I’m trying to say is, for the enterprise, does WordPress still maintain that kind of pride place, top of the tree, or are you struggling to find new clients?

[00:30:28] K. Adam White: We’re not struggling to find new clients. We’re lucky that we’re doing quite well on marketing, and we also have had a very powerful year in terms of building relationships with new enterprises, and finding ways to take the technology that we believe in and solve their problems with it.

But I would argue that WordPress has never been the top of the enterprise space. And this actually goes back to your question about what is there that might be missing inside WordPress. The biggest thing that I think someone gets from a more, I’m going to use the term loosely, traditional enterprise CMS, is control.

And WordPress has a security model where the ability to edit and publish a piece of content is usually at the post level. There’s ways to add specific permission checks for metadata. There’s ways that you can restrict what’s accessible and editable with custom interfaces and custom API endpoints. But we tend to have things fall down to the capability checks for user can edit post 1, 2, 3. Yes. No.

And that means that if you have a user profile where your organisation depends on someone being able to come in and touch only the headlines and the SEO metadata, we don’t really have a model for that right now in WordPress.

Whereas something like Sitecore, each individual, almost at the level of every string on the site, whether it’s a set of paragraphs or the label of a button, ends up as a individual node in the content tree. And those can be granted or denied to certain users on a much more granular level. So that to me is a bridge that I still am excited to see what we can do within WordPress to maybe build better interfaces, or better primitives in the editor.

Block locking helps a little bit, but it is an API that’s quite difficult for some teams to wrap their heads around. And it also doesn’t really change the fact that if you can edit the post, and you were able to get the code editor up, then if you’re able to save it, you’re able to save it and doesn’t really go block by block. You’d have to write custom validation or permissions logic in order to be able to reject and update based on the user if they’re editing a block that is next to the one that they were supposed to.

[00:32:32] Nathan Wrigley: So do you have to present to the clients? It’ll be fine. This is what WordPress has. Don’t worry too much about it. If you’ve got this permission, yep, sure. You might be able to overlap and think people could delete things or modify things that perhaps they wouldn’t have to. That’s an educational piece on your side. Go and teach everybody not to mess around with things that they shouldn’t be messing around with.

But you would wish that in WordPress you could assign, say, as you described, this H1, this person can amend it, and this person can access the colour palette for the background image over here, but they can’t access the text. That kind of really granular permission. Whereas block locking just, it seems a bit more of a blunt instrument if you know what I mean. It’s binary. It’s locked or it’s not. You’d like to unlock the capabilities within each block so that certain users can do certain things within the same block.

[00:33:15] K. Adam White: Within blocks, we tend to rely on security through obscurity. We can hide or obfuscate controls behind block locking with content only. We can hide them behind patterns. But if someone’s coming to WordPress, we do make sure that they understand upfront what the nuance of control will be. And we will work with them usually to make things more editable.

Again, I will mention that most of the projects that we get that come from one of these more control-oriented CMSs into WordPress, what they’re seeking is actually more flexibility, not less. So they’re making a decision that they are willing to exchange the stringent control that they get in their existing tool for a process-based change. Maybe they add a review step, or add some sort of workflow plugin, so that we can validate that things look good and have someone sign off on it before it gets published. They would prefer to go that route than to sacrifice the ability for the editors to have the full control, and full pallet of options available to them.

[00:34:13] Nathan Wrigley: Right, so that’s a much more loose approach. Everybody can maybe do more than they ought to do. If we have some editorial guideline where that can’t finally hit the public domain because the publish button is unavailable to you, that’s, okay. We’ll accept that kinda halfway house, if you like. That’s interesting.

[00:34:30] K. Adam White: Each client’s needs are going to be slightly different. We do layer in publication checklists. We have tools to be able to say, this has to be tagged with the primary category before it goes live. We have tools to say, this still has lorum ipsum in it. You can add those in and build workflows, but I tend to like to help clients build processes to support those, rather than trying to take a draconian approach and lock everything down. Because then your work is going to be constantly chasing fine-grained permissions controls when you could be working to use that time making sure that all of the editors know what they can do.

[00:35:04] Nathan Wrigley: I just want to drill into this a bit more. I know this isn’t where we were supposed to go, but I find it really interesting. Would you like those things to ship in Core? obviously they suit you down to the ground, all of those granular permissions, but do you think that belongs in Core?

[00:35:17] K. Adam White: I think that we need more workflow in Core.

[00:35:20] Nathan Wrigley: Okay.

[00:35:20] K. Adam White: I know that there’s a number of different agencies and hosts which each have developed our own workflows solutions. I’ve worked across a number of them on projects that I’ve helped to support.

But the notion that if you have something published and you make an edit out of the box, WordPress will automatically put live any further changes that you make to a published post when you hit save. That is probably the single thing that we most frequently have to build some type of plugin into a site to handle.

Because we need to be able to give people an editorial review step. So that is something that I think we have a number of good tools, but I would love to see a more opinionated default in Core that we can use as a foundation for more complicated post editorial workflow. I think that’s the thing that we most frequently run into. That, and also I guess internationalisation are probably the two things that hopefully will come to the surface of the WordPress roadmap over time.

[00:36:13] Nathan Wrigley: Yeah, I’d really not thought about that. Given Human Made’s sort of credentials and what have you. Do you have a lot of clout? Do you just punch above your weight in conversations about what makes it into Core? Do you get involved in those discussions? I’ve literally no idea how that would happen. Do you communicate to people when a release is coming around. Do you have a voice? Do you make yourself available? What is Human Made’s position in terms of getting things pushed into Core?

[00:36:37] K. Adam White: We participate in the project. I personally have been less involved in Core over the past several years than I would have hoped. I’ve been very much enjoying the detailed, quite close to the ground work that I’m doing on our agency projects. But unfortunately, I have taken a bit of a step back on the open source project.

Some of my colleagues are in a slightly different boat. My colleague, John Blackbourn, our Director of Security for our own hosting product is also the head of the Security Team for WordPress? And has been helping us get the core patches out for the recent set of security releases.

We obviously will advocate in calls for feedback within the Gutenberg project when we feel that there’s a particular direction that we see from our projects. We are able to provide feedback on the UI, and the capabilities of new blocks that are being proposed. But that’s all done through the normal Gutenberg GitHub issue, and WordPress

[00:37:28] Nathan Wrigley: So I think we should probably knock it on the head there. We’ve reached our allocated time. I’ll just point out that these days, it used to be the case that if I was at a WordCamp, you’d really have to wait about six months before the video for the presentation was available. I’m pretty sure it’ll be done already, in all honesty. 24 hours seems to be the time there. So if you were to go to WP Tavern, I will make sure that the link to the video, of K. Adam is there. If not, you can probably go to Google and search Migrating to Blocks, and in parenthesis, with Artisanal Care at Industrial Scale, and you’ll be able to see what it is that K. Adam was talking about.

But really, thank you so much for chatting to me today about all of that.

[00:38:06] K. Adam White: Thank you very much. And I can confirm that the video is already live on YouTube.

On the podcast today we have K. Adam White, or K. Adam for short.

K. Adam is the principal engineer at Human Made, an enterprise WordPress consultancy. He’s been involved with WordPress almost 20 years, attended his first WordCamp in Boston back in 2011, and has contributed to WordPress Core and the broader open source ecosystem. Human Made is known for delivering complex projects, think high stakes, no room for mistakes, from global brands moving to WordPress.

This time around, K. Adam delivered a presentation at WordCamp US focused on a crucial topic for anyone modernising their site, migrating to blocks. Human Made has been all-in on the block editor since the Gutenberg plugin days, and the team now specialises in large-scale migrations from other content management systems like Sitecore, as well as from other WordPress page builders.

Our conversation focused on the technical and editorial challenges of moving tens or hundreds of thousands of posts into the world of blocks and patterns. We talked about the need to combine “artisanal care”, attention to detail in design, layout, and brand, with “industrial scale”, the ability to automate, audit, and validate mass migrations without losing visual fidelity.

We also discussed the use of patterns as a foundation for development, integrating custom and Core blocks, and leveraging new tools (including AI-powered agents and open source plugins like Human Made’s own rehydrator) to streamline migration workflows. We also touched upon how clients are onboarded, the process of auditing legacy content, strategies for training editorial teams on the block editor, and there’s a frank reflection on gaps in WordPress, like granular content permissions.

If you’re contemplating a move to the block editor, wrestling with a massive content migration, or curious about what happens when enterprise complexity meets the flexibility of WordPress, this episode is for you.

Useful links

Human Made

Migrating to Blocks (With Artisanal Care, at Industrial Scale) – K. Adam’s presentation at WordCamp US 2026

Human Made’s rehydrator plugin on GitHub

💾

Organizations Are Now Reaching for OpenSearch for AI, Not Just Search

22 September 2026 at 16:41
linux foundation and opensearch report banner

That's very interesting to see considering OpenSearch began as a fork.

When Elastic relicensed Elasticsearch and Kibana in 2021, AWS built an open alternative, keeping it under the Apache 2.0 license. Three years later, the project moved to neutral governance after the Linux Foundation launched the OpenSearch Software Foundation in September 2024 as its vendor-neutral steward.

Now, reflecting on the journey so far, Linux Foundation Research and the OpenSearch Software Foundation have jointly published The 2026 Open Data Infrastructure Report, examining how organizations are building out data infrastructure and what role OpenSearch plays in that picture.

The survey, conducted in May 2026, covered 294 respondents across diverse categories like IT vendors, end-user organizations, and independent consultants.

The report, briefly

Generative AI and LLM-powered applications lead all AI use cases at 82% of organizations surveyed.

At least 83% of respondents across every region are already running AI workloads or have plans to. Among current OpenSearch users, 62% are already using it in AI workloads, and 44% consider it core AI infrastructure rather than a supporting component.

By 2026, 89% of organizations had heard of OpenSearch, up from 68% two years prior. Production deployments went from 19% to 36% over the same period, with another 36% running tests or assessing adoption.

Cost and vendor independence are what organizations weigh most when picking a data infrastructure platform. Total cost of ownership tops the selection criteria for 80% of organizations, security and compliance for 79%, and vendor independence for 69%.

71% also say running infrastructure outside any single cloud provider's control is a strategic priority for their organization, while average annual data infrastructure spend across the sample sits at around $2.4 million.

Among active users, search and retrieval leads at 91%, followed by log analytics and observability at 83%, real-time analytics at 70%, and AI-related workloads at 62%.

Whereas hybrid search is the go-to approach for 68% of organizations.

What now?

Most current deployments are not yet deeply embedded. Six in ten users say their OpenSearch setup is either experimental or something they could swap out; only 36% call it deeply embedded or mission-critical.

Among non-users, 81% say they are open to evaluating OpenSearch, though only 14% are actively planning to do so.

Alongside the report, the OpenSearch Software Foundation has announced three new members; one of them being Intel, and the other two being the new long-term support vendors.

We asked Bianca Lewis, Executive Director of the OpenSearch Foundation, what she thought about where agentic AI's headed next and how OpenSearch would fit into it:

The technology stack powering agentic AI is shifting rapidly, and with growing uncertainty around AI costs, long-term commitments to proprietary platforms present both a financial and architectural risk. Now, leaders are turning to an open, vendor-neutral platform to strategically mitigate risk.
An open data layer provides cost data and full visibility into which services are being called, giving teams the clarity needed to accurately cost and manage their infrastructure.

This delivers the flexibility to innovate without vendor lock-in, ensuring organizations maintain sovereignty over both their data and their spend as the future of AI takes shape.

Enterprise WordPress Security Is Really About Decision Making

30 July 2026 at 08:35

Enterprise WordPress security is often discussed in technical terms.

Keep software up to date. Strengthen authentication. Monitor vulnerabilities. Choose secure infrastructure. Follow security best practices.

They’re all sensible recommendations.

The difficulty is that very few enterprise platforms become more or less secure because of a single technical decision. They change gradually as the organisation around them changes.

A new supplier joins a project. Marketing adopts another platform. A regional office needs its own publishing workflow. A business acquisition introduces another website. An AI tool is connected to editorial processes. Someone needs temporary access to production for a launch weekend.

None of these decisions appear particularly significant. They’re simply part of running a large organisation.

Taken together, they shape the security of the platform far more than many people realise.

In practice, enterprise WordPress security is heavily influenced by how organisations make decisions over time.

Enterprise WordPress security involves every team

One of the defining characteristics of enterprise organisations is that nobody sees the whole picture.

Editorial teams see publishing workflows. Developers see code and infrastructure. Marketing sees campaigns and customer journeys. Procurement sees contracts. Security teams see policies and risk. Regional teams see the systems they rely on every day.

Each perspective is valid. Each team is solving genuine business problems.

The challenge is that every decision made within those individual contexts also affects the wider platform.

A new integration might improve a marketing workflow while introducing another dependency that engineering needs to maintain. An AI service might reduce editorial effort while creating a new relationship with organisational data. A supplier might solve an immediate delivery challenge while increasing the number of people with access to production systems.

None of those outcomes necessarily make the platform less secure. They do illustrate why enterprise WordPress security extends well beyond the CMS itself. The platform becomes the point where hundreds of independent decisions intersect.

Enterprise WordPress platforms remember decisions long after projects end

Enterprise platforms have long memories.

Projects finish. Teams change. Agencies move on. Priorities shift. The platform remains.

Several years after launch, it’s common to find systems that nobody uses anymore, integrations whose original owners have left the organisation, or workflows that continue simply because they’ve never been revisited.

Sometimes those decisions still make sense. Sometimes the business has changed so much that nobody remembers why they were made in the first place.

This isn’t unusual. It’s how successful enterprise platforms evolve.

The organisations that manage this complexity well don’t rely on institutional memory. They create processes that make it easier to understand why decisions were made, who owns them today, and when they should be reviewed.

That’s an operational discipline as much as a security one, and it’s an important part of maintaining enterprise WordPress security over the lifetime of a platform.

AI is reshaping enterprise WordPress security

AI is becoming an increasingly important part of enterprise WordPress security discussions.

Teams that might previously have evaluated one or two new technologies each year are now assessing new AI capabilities every month. Editorial teams want content assistants. Developers are experimenting with coding agents. Marketing wants personalisation. Customer service teams are exploring conversational interfaces.

Each opportunity brings another decision.

Which provider should we use? What content should it access? Which teams can use it? How will it integrate with existing systems? Who remains accountable for the output? What happens if the organisation wants to adopt a different model next year?

These questions rarely have purely technical answers.

They require organisations to make consistent decisions across technology, operations, legal, procurement, marketing, and security. The faster AI evolves, the more valuable that consistency becomes.

What does enterprise WordPress security actually involve?

When people think about enterprise WordPress security, they often picture software updates, infrastructure, or vulnerability management.

Those are all essential, but they’re only part of the picture.

A mature approach to enterprise WordPress security also includes:

  • Governance and decision-making
  • Identity and access management
  • Integration and supplier management
  • Operational processes
  • AI governance
  • Change management
  • Clear ownership and accountability

Together, these practices help organisations maintain confidence as platforms evolve, technologies change, and digital estates become more complex.

Governance exists to improve decisions

Governance often sounds administrative.

Policies. Documentation. Approval processes. Standards.

Viewed that way, it’s easy to see governance as something that slows organisations down.

Enterprise organisations experience it differently.

Good governance reduces uncertainty. Teams understand how new technologies are evaluated. Suppliers know what’s expected of them. Decisions follow consistent principles rather than depending on who happens to be involved in a particular project. Similar problems are solved in similar ways, even when different teams are responsible for delivery.

That consistency becomes increasingly valuable as organisations grow because the volume of decisions continues to increase while the number of people making them grows alongside it.

Strong enterprise WordPress security depends on organisations making consistent decisions over many years.

Ultimately, enterprise WordPress security reflects how an organisation operates

Every enterprise platform tells a story about the organisation behind it.

Some platforms reveal years of carefully considered evolution, where new technologies have been introduced deliberately and operational practices have matured alongside the business.

Others reveal the opposite. Different teams have solved similar problems in different ways. Ownership has become unclear. Temporary decisions have quietly become permanent. Complexity has accumulated faster than understanding.

The technology may look similar in both cases.

The difference lies in how decisions have been made.

This is why enterprise WordPress security shouldn’t be viewed solely as a technical capability. It reflects how an organisation introduces change, manages complexity, and creates confidence that today’s decisions will still make sense several years from now.

The post Enterprise WordPress Security Is Really About Decision Making appeared first on Human Made.

WordPress Security and AI: the Attack Surface Is Expanding

By: Jon Ang
14 July 2026 at 13:25

Every month, enterprise organisations connect more AI systems to their digital estate.

For organisations running WordPress at enterprise scale, these new services are changing the security landscape. AI assistants, content generation tools, developer agents, search experiences, and workflow automations increasingly interact with WordPress content, APIs, and business systems. Each new integration creates opportunities for innovation alongside new security considerations that platform and security teams need to understand.

The attack surface is no longer defined solely by websites, applications, or infrastructure. It increasingly includes every AI service that can access, process, or generate information on behalf of the organisation.

This shift is changing the questions enterprises need to ask about WordPress security and AI. As AI becomes more deeply embedded in enterprise publishing, development, and operational workflows, organisations need to understand how these technologies influence security, governance, and risk.

WordPress security and AI start with understanding data access

Every AI tool depends on access to information.

In enterprise WordPress environments, that information often includes editorial content, media libraries, customer data, product information, internal documentation, and the wider business systems connected to the platform. AI tools derive their value by accessing, analysing, or generating content from these sources.

Each connection creates a new relationship between enterprise data and a third-party service.

On its own, an individual integration may present relatively little risk. Over time, however, organisations can accumulate dozens or even hundreds of AI-powered services across different departments, each with its own permissions, governance requirements, and security considerations.

Marketing teams may use AI to generate campaign content. Editorial teams may rely on AI for summarisation or tagging. Developers increasingly use AI assistants to write and review code. Customer service teams are deploying AI-powered support tools, while business teams connect AI to internal knowledge and operational data.

The result is a growing network of systems with access to valuable organisational information.

Understanding how those systems interact with WordPress and the wider digital estate is becoming an increasingly important part of enterprise security.

Visibility is becoming harder to maintain

Many enterprise security programmes were designed around relatively stable technology estates.

Applications were centrally approved. Infrastructure evolved gradually. New software typically followed established procurement and governance processes.

AI adoption often follows a different path.

Teams can begin experimenting with new tools in minutes. Individual departments may adopt different providers to solve similar problems. New capabilities appear faster than many organisations can evaluate them.

Innovation accelerates. Visibility can diminish just as quickly.

For organisations running WordPress, maintaining visibility means understanding where AI is being used, what information those systems can access, and how data moves between WordPress and the wider digital estate. Without that visibility, it becomes increasingly difficult to assess risk, maintain compliance, or respond confidently as the technology landscape evolves.

Data governance is becoming a WordPress security priority

As organisations adopt more AI services, governance becomes increasingly important.

Questions that once focused primarily on infrastructure now extend to AI itself.

  • Which AI tools are approved?
  • What information can employees share with AI systems?
  • Which WordPress content and business systems can AI access?
  • Who is responsible for reviewing new AI services?
  • How are permissions, data flows, and usage monitored over time?

These questions sit at the intersection of technology, governance, and WordPress security.

The organisations making the greatest progress with AI are often those that establish clear policies early, allowing teams to innovate within well-understood boundaries rather than introducing controls after widespread adoption.

WordPress provides the flexibility to adopt AI securely

The AI landscape continues to evolve at extraordinary speed.

New models emerge regularly. Existing providers introduce new capabilities. Organisations are discovering new use cases while reassessing others. Few enterprises expect to be using exactly the same AI technologies five years from now.

This places greater importance on the flexibility of the platforms that sit at the centre of the digital estate.

WordPress is well suited to this environment because it was designed to integrate with other systems. Its mature API ecosystem, open architecture, and flexibility allow organisations to introduce new AI services while maintaining control over infrastructure, governance, and data flows.

That flexibility also supports long-term resilience. Enterprises can evaluate new AI providers, replace existing services, or introduce new capabilities without being constrained by proprietary platform limitations or tightly coupled technology stacks. As AI continues to evolve, retaining that freedom of choice becomes an increasingly important aspect of enterprise WordPress security.

Good WordPress security has always been about governance

Discussions about WordPress security and AI often focus on technology. In practice, successful enterprise programmes are built on governance, operational discipline, visibility, and the ability to adapt as the organisation evolves.

AI reinforces something enterprise security teams have understood for years.

Strong WordPress security is rarely determined by a single technology choice. It emerges from governance, operational discipline, visibility, and the ability to adapt as the organisation evolves.

The introduction of AI doesn’t change these principles. It extends them across a larger and more complex technology landscape.

Organisations that establish clear ownership, understand how information flows between systems, and maintain visibility across their digital estate will be better placed to adopt AI confidently while protecting their platforms, users, and data.

As enterprise AI adoption continues to accelerate, the organisations achieving the strongest security outcomes are unlikely to be those that slow innovation. They will be the ones that build the governance, operational maturity, and platform flexibility needed to evolve securely over time.

The post WordPress Security and AI: the Attack Surface Is Expanding appeared first on Human Made.

Why Enterprise WordPress RFPs Often Miss What Matters

By: Jon Ang
2 July 2026 at 08:13

Choosing an enterprise WordPress agency should be a straightforward process. Define your requirements on the RFP, invite proposals, compare responses, and select the partner that best fits your needs.

In reality, it’s rarely that simple.

Most enterprise buyers aren’t choosing between obviously good and obviously bad agencies. They’re choosing between several capable teams with strong portfolios, recognisable clients, and seemingly similar approaches. On the surface, many proposals look remarkably alike.

The challenge is that some of the factors that have the biggest impact on long-term platform success are also the hardest to evaluate during procurement.

A platform can launch on time, meet its requirements, and still become difficult to evolve a year later. Editorial workflows can become frustrating. Governance can start to break down. New features can take longer and cost more to deliver than expected. None of these problems tend to appear in an agency’s case studies, and they’re rarely exposed by a traditional RFP process.

That’s why enterprise buyers need to look beyond deliverables and ask a deeper question: what will it actually be like to operate and evolve this platform over the next five years?

The things RFPs measure well

Procurement processes are designed to create structure and consistency. They help organisations compare agencies against the same criteria and provide stakeholders with confidence that decisions are being made fairly.

Many of the things they evaluate are important.

Relevant experience matters. A team that has worked with large publishers, universities, government organisations, or global brands is likely to understand challenges that smaller agencies may never have encountered.

Technical capability matters too. Enterprise platforms need strong engineering foundations, sensible architecture, reliable deployment processes, and a clear approach to performance, accessibility, and security.

Commercial models, timelines, team structures, and delivery methodologies all deserve scrutiny.

The problem isn’t that these things are unimportant. The problem is that they only tell part of the story.

The things that matter most are harder to score

Enterprise platforms are shaped as much by organisational realities as technical requirements.

A publisher operating across multiple markets may need to balance central governance with local editorial autonomy. A university may have hundreds of stakeholders with different priorities and levels of technical expertise. A large enterprise may need to satisfy compliance requirements while integrating with a growing ecosystem of internal systems and third-party services.

Two organisations can ask for almost identical platforms and face completely different delivery challenges because of the way they operate internally.

This is where agency evaluation becomes more complicated.

How does an agency handle competing stakeholder priorities? What happens when requirements change significantly during delivery? How do they approach governance for large editorial teams? How do they prevent technical debt from accumulating over the lifetime of a platform?

These questions are harder to compare in an RFP spreadsheet, but they often have a greater influence on long-term outcomes than the features listed in the original scope.

Don’t treat it as a checklist

An RFP is a choice of partner, not a set of answers

There’s a temptation to treat an RFP as a checklist: a fixed list of requirements, a column of responses, a shortlist that falls out of the scoring. But that framing quietly assumes the important decisions have already been made, and that all an agency has to do is confirm it can execute them.

That is rarely why an enterprise RFP exists. Most enterprise RFPs are written at precisely the moment it becomes clear that external help is needed. That is worth sitting with. If an organisation already knew the right technical direction, the right sequencing, and the right trade-offs, it wouldn’t be going to market in the first place. The RFP is an acknowledgement that the answers aren’t fully in the room yet. Which makes it strange to then lock those answers down before the conversation with a partner has even begun.

The value a strong agency brings is a current and varied set of data. They have seen the same problem across many organisations, watched approaches age well or badly, and can tell you which of your assumptions are load bearing and which are simply habit. A checklist cannot capture that, and an RFP that only measures compliance against a fixed specification throws most of it away.

So an RFP that ends up dictating the entire technical direction does the buyer a disservice. It converts a moment of real openness into a procurement formality, and it selects for agencies that are good at agreeing rather than agencies that are good at thinking.

The better goal is narrower and harder. Not to find someone who will build exactly what you have already specified, but to choose the right partner to help you work out the right things to do.

Look at how agencies think, not just what they build

One of the most useful things an agency can demonstrate during procurement is how it approaches complexity.

Experienced enterprise partners tend to ask different questions. They’re interested in workflows, approval processes, governance structures, ownership models, and operational constraints. They want to understand how content is created, who makes decisions, and where bottlenecks exist today.

This isn’t curiosity for its own sake. It’s because enterprise projects rarely become difficult for purely technical reasons.

Platforms become difficult when technology, people, processes, and organisational priorities fall out of alignment.

An agency that understands this will spend less time selling solutions and more time understanding the environment those solutions need to support.

That’s often a stronger indicator of future success than a polished proposal deck.

Pay attention to how they discuss trade-offs

Enterprise delivery involves constant trade-offs.

Flexibility and governance need to coexist. Editorial freedom needs to be balanced with consistency. Technical ambition needs to be weighed against long-term maintainability.

Strong agencies are comfortable discussing these trade-offs openly.

Rather than presenting every decision as obvious, they explain the implications of different approaches. They talk about risks as well as opportunities. They recognise that there is rarely a perfect solution, only solutions that are more or less appropriate for a particular organisation.

This kind of conversation is valuable because it reveals how an agency will behave once delivery begins.

Will they help stakeholders make informed decisions? Will they challenge assumptions when necessary? Will they surface risks early?

These behaviours become increasingly important as projects grow in complexity.

Think beyond launch

Many procurement processes are understandably focused on the project immediately in front of them.

Enterprise platforms have much longer lifecycles.

New teams join. Business priorities change. Additional integrations are introduced. Governance evolves. Expectations grow. The platform that launches this year will need to support requirements that haven’t even been identified yet.

The best agency partners think about this from the beginning.

They make architectural decisions with future change in mind. They consider how workflows will scale as teams grow. They help organisations build sustainable governance models rather than solving only the immediate problem.

Most importantly, they recognise that launch is not the moment a platform proves its value. A platform proves its value through its ability to keep evolving without becoming slower, more expensive, or more difficult to manage.

A better procurement question for RFPs

When evaluating agencies via RFP, it’s natural to ask whether they can deliver the project you’ve defined. Evaluating their technical skills will also be high on the priority list.

Enterprise buyers should ask something else as well.

Can this agency help us operate and evolve this platform over the next five years?

That question changes the conversation.

It shifts attention away from features and towards adaptability. It encourages buyers to look beyond delivery plans and understand how agencies think about governance, platform evolution, organisational complexity, and long-term sustainability.

Those are the areas where the biggest differences between agencies often emerge.

They’re also the areas that have the greatest influence on whether a platform continues creating value long after the launch announcement has been published.

Choosing an enterprise WordPress partner is one of the most important decisions you’ll make for your platform.

If you’re planning a replatform, reviewing agency options, or simply trying to understand what good looks like at enterprise scale, we’d be happy to share our experience.

Get in touch to discuss your project.

The post Why Enterprise WordPress RFPs Often Miss What Matters appeared first on Human Made.

Enterprise CMS Costs: What Total Cost of Ownership Really Means

26 June 2026 at 09:34

Enterprise platform discussions often begin with software costs.

Licence fees, subscription models, implementation budgets, and support agreements are relatively easy to compare during procurement. They are visible, measurable, and usually well documented by vendors.

The challenge is that software costs represent only one part of a platform’s economic impact. Once a platform is embedded across teams, workflows, and business processes, a much broader set of costs begins to influence its value.

Integrations need maintaining. Governance models need evolving. New channels emerge. Teams expand into new regions. Business priorities shift. Technologies that were not part of the original requirements become important.

Over time, these factors often have a greater influence on platform economics than the original software agreement.

This is why enterprise organisations increasingly evaluate platforms through the lens of total cost of ownership (TCO).

The largest platform costs often emerge after launch

Many digital platforms begin with a relatively clear set of requirements. A website needs to be rebuilt. A content platform needs modernising. Multiple properties need consolidating onto a shared foundation.

Those projects have a defined scope and budget.

The complexity arrives later.

As organisations grow, digital platforms become connected to a wider ecosystem of services. Content management systems frequently sit alongside customer data platforms, analytics tools, ecommerce services, identity providers, DAM systems, marketing automation platforms, translation workflows, and increasingly, AI-powered tools.

Each integration creates value. Each integration also introduces dependencies that require maintenance, governance, and operational oversight.

At enterprise scale, platform ownership becomes less about running a CMS and more about managing an evolving digital ecosystem.

Understanding how a platform supports that evolution is central to understanding its long-term cost profile, and thus the total cost of ownership.

Why platform flexibility has financial value

Enterprise requirements rarely remain static for long.

A business may acquire a new brand, expand into a new market, launch a new product line, or introduce entirely new customer experiences. Regulatory requirements change. Internal operating models evolve. New technologies create opportunities that were not anticipated when the platform was first selected.

Every one of these developments places demands on the underlying platform.

Some platforms accommodate change relatively easily. Others require significant redevelopment, specialist expertise, or commercial agreements before new capabilities can be introduced.

The difference has a direct financial impact.

When introducing a new integration takes months rather than weeks, costs increase. When teams are forced to work around platform limitations, productivity declines. When architectural decisions made years earlier restrict future options, innovation becomes slower and more expensive.

This is one reason enterprise leaders increasingly assess a platform’s adaptability alongside its feature set.

Understanding the economics of proprietary platforms

Proprietary platforms provide a clear commercial model. Organisations pay for access to software that is owned, developed, and governed by a vendor.

For many businesses, this structure offers reassurance. Product roadmaps, support models, and accountability are clearly defined.

As digital estates grow, however, the relationship between platform usage and platform costs often becomes more complex.

Licensing models frequently scale alongside adoption. Additional users, environments, websites, markets, or capabilities may introduce additional costs. Access to advanced functionality may require higher pricing tiers. Integrations and customisations can become dependent on vendor-approved approaches or specialist expertise.

None of this is unusual. It reflects the incentives built into commercial software businesses.

The important consideration for enterprise buyers is how those costs behave over time. Growth, complexity, and change are constant features of large organisations. Understanding how a platform responds to those forces is often more valuable than comparing feature lists during procurement.

Where open source creates a different economic model

Open source platforms approach the same challenge from a different direction.

Rather than charging for access to the software itself, open source shifts investment towards implementation, operations, and capability development. Organisations retain ownership of their code, data, infrastructure decisions, and platform architecture.

This changes how investment is allocated.

Budget that might otherwise be committed to recurring licensing costs can be directed towards improving editorial workflows, strengthening integrations, enhancing customer experiences, modernising infrastructure, or introducing new capabilities. The organisation has greater discretion over where resources are invested and how priorities are balanced.

Control also extends beyond budgeting.

Teams can choose hosting providers, adopt new technologies, work with different implementation partners, and evolve their architecture as requirements change. Decisions are shaped by business priorities rather than vendor roadmaps or commercial constraints.

For enterprise organisations operating in environments where change is constant, that flexibility has practical and measurable value.

Vendor lock-in is an operational and financial consideration

Vendor lock-in is often discussed as a technical issue, but its effects extend much further.

Organisations that become heavily dependent on a single vendor ecosystem can find future decisions increasingly constrained. Replacing services becomes more difficult. Negotiating commercial agreements becomes more challenging. Migrating data or introducing alternative technologies requires greater investment.

These constraints affect both risk and the total cost of ownership.

By contrast, platforms built on open standards and open technologies provide more options when business requirements change. That does not eliminate complexity, but it does reduce dependency on a single supplier or ecosystem.

For many enterprise leaders, preserving optionality has become a strategic objective in its own right.

The cost that rarely appears in TCO models

One area that receives relatively little attention in platform evaluations is the cost of delayed innovation.

Organisations compete through their ability to adapt. New products, services, workflows, and customer experiences all depend on how quickly teams can turn ideas into reality.

When platform constraints slow experimentation, the impact is rarely captured in procurement spreadsheets. Lost opportunities do not appear as line items. Delayed launches rarely show up in platform budgets.

Their effect is still significant.

Teams that can test new ideas quickly tend to learn faster. Organisations that can integrate emerging technologies more easily tend to adapt more effectively. Platforms that support continuous evolution create fewer barriers between strategy and execution.

These advantages accumulate over time.

A broader view of return on investment

Enterprise platform decisions influence far more than technology stacks.

They affect how teams collaborate, how quickly organisations can respond to change, how easily new capabilities can be introduced, and how much control businesses retain over their digital future.

Viewed through that lens, total cost of ownership becomes a measure of resilience and adaptability as much as financial efficiency.

The most valuable platforms are rarely those that simply minimise costs. They are the platforms that allow organisations to evolve without repeatedly rebuilding, replatforming, or renegotiating the foundations of their digital estate.

Download The Enterprise WordPress Playbook to explore platform strategy, governance, composable architecture, AI adoption, and the factors that shape long-term enterprise platform success.

Animal, Bee, Insect
Advertisement, Poster, Animal

Download The Enterprise WordPress Playbook to explore platform strategy, governance, composable architecture, AI adoption, and the factors that shape long-term enterprise platform success.

The post Enterprise CMS Costs: What Total Cost of Ownership Really Means appeared first on Human Made.

Why platform evolution beats replatforming

30 April 2026 at 10:14

Enterprise platform decisions are often framed as a choice between build or buy. Either you invest in something bespoke, or you purchase a proprietary system that promises speed and structure.

But for many enterprise organisations, that framing no longer fits.

Digital platforms now have to support multiple brands, markets, teams, channels, integrations, and increasingly, AI-enabled workflows. Requirements change quickly. New services need to be added. Legacy systems need to be replaced gradually. Teams need to move faster without losing control.

In that environment, the strongest platform strategy is not always to rebuild from scratch or commit to a single vendor-led roadmap. It is to evolve.

The limits of traditional replatforming

Large-scale replatforming projects often begin with good intentions. The current platform feels too slow, too expensive, or too difficult to change. A new system promises a clean break.

The problem is that enterprise complexity doesn’t disappear when a platform changes. It moves.

Content models, integrations, governance, editorial workflows, compliance requirements, performance needs, and internal processes all still need to be understood and supported. A big-bang migration can create risk, delay value, and force teams to make decisions before they have had a chance to test what works.

By the time the new platform is live, requirements may already have shifted.

Why evolution is a better fit for modern digital teams

An evolution-led approach treats platform change as an ongoing process, not a one-off transformation.

Instead of replacing everything at once, organisations build on a flexible foundation and improve it over time. Capabilities can be added, replaced, or refined as business needs change. Integrations can be modernised in stages. Teams can validate decisions earlier and reduce disruption.

This is where open platforms like WordPress are especially powerful.

WordPress gives enterprises the ability to shape the platform around their needs, rather than adapting their organisation to fit a fixed product model. It can support traditional, headless, hybrid, multisite, and composable architectures, depending on what each part of the business requires.

Flexibility reduces long-term risk

At enterprise scale, the cost of change matters.

A platform that is quick to launch but difficult to adapt can become expensive over time. Licensing tiers, constrained integrations, vendor dependencies, and customisation limits all affect how easily an organisation can respond to new priorities.

Open architecture changes the equation.

With WordPress, teams can change hosting providers, integrate specialist tools, adopt new services, and evolve workflows without being tied to a single vendor’s roadmap. That flexibility reduces lock-in and gives organisations more control over both cost and direction.

Evolution supports better governance

Continuous evolution doesn’t mean uncontrolled change.

In fact, it works best when governance is built in from the start. Shared standards, reusable components, role-based permissions, approval workflows, security practices, and clear ownership models all help distributed teams move quickly while staying aligned.

For global, multi-brand, or multi-language organisations, this balance is critical. Central teams can maintain consistency while local teams retain the flexibility to serve their own markets.

The role of WordPress in an evolving enterprise stack

Modern enterprise platforms rarely operate alone. They sit within a wider ecosystem of DAMs, CDPs, analytics tools, commerce platforms, search services, and AI providers.

WordPress fits naturally into this kind of composable architecture. It can act as the content layer, the publishing interface, the integration point, or part of a wider digital experience platform.

That makes it well suited to phased change. Organisations can start with a focused use case, prove value, then expand over time.

From replacement mindset to evolution mindset

The most successful enterprise platforms aren’t static; they improve continuously.

That requires a shift in mindset. Instead of asking which platform will solve every problem today, leaders should ask which platform gives them the most room to adapt tomorrow.

For many organisations, WordPress provides that foundation: open, extensible, widely adopted, and capable of supporting complex digital operations at scale.

Replatforming may still be necessary. But the goal should not be another fixed end state.

The goal should be a platform that can keep changing.

The post Why platform evolution beats replatforming appeared first on Human Made.

Evaluating the Technical Skills of a WordPress Agency

6 May 2026 at 13:07

For non-technical stakeholders, choosing a WordPress agency can feel like guesswork.

Most agencies sound convincing. Many have polished portfolios. Pricing varies wildly. And without a technical background, it is difficult to separate genuine engineering expertise from surface-level competence.

That gap matters.

The technical decisions made early in a WordPress project shape everything that follows: performance, scalability, security, editorial experience, and long-term cost. Two sites can look identical at launch and behave completely differently six months later.

We’re here to help you spot that difference.

Why technical depth matters more than you think

At a glance, most WordPress builds look similar. Under the surface, they rarely are.

Less experienced agencies tend to optimise for speed of delivery. That often means leaning heavily on page builders, stacking plugins, or introducing custom code that bypasses WordPress conventions. It works, until it doesn’t.

What that usually leads to:

  • performance that degrades as the site grows
  • updates that break critical functionality
  • security exposure through poorly maintained dependencies
  • rising maintenance costs over time
  • difficulty integrating with other systems
  • less editorial flexibility and creativity
  • developer support is required for simple content or design updates

More mature teams take a different approach. They build with WordPress, understand its capabilities and are close to its evolving roadmap. They make fewer shortcuts early on, so you aren’t paying for them later.

The difference is rarely visible in a demo. It becomes obvious in ownership.

WordPress core alignment and contribution

A simple way to gauge technical maturity is to look at how an agency relates to WordPress itself.

WordPress isn’t static. It evolves continuously through an open-source community. Agencies that stay close to core benefit from that evolution. Agencies that fight it tend to carry increasing technical debt.

You are looking for alignment, not reinvention.

Strong signals include a preference for native functionality, a clear awareness of upcoming changes, and an absence of unnecessary abstraction layers. The best teams will also contribute back, whether that’s to core or the wider ecosystem. The Five for the Future pledge database is a great resource for checking which organisations have made a commitment to contribute regularly.

That contribution matters. It’s one thing to use WordPress; it’s another to help shape it.

If you are not sure how to assess this, ask directly:

  • Do you contribute to WordPress?
  • How do you stay aligned with core updates?
  • Where have you deliberately chosen core over custom?

Clarity and intent are more important than perfect answers. There’s got to be an obvious culture of contributing from the top down.

Modern WordPress: Full Site Editing and the block editor

WordPress has changed significantly. Not every agency has kept up.

The block editor and Full Site Editing represent a shift towards a more flexible, system-driven way of building sites. They’re more than new tool: they change how content teams work and how sites evolve.

Get the whole story on Full Site Editing and what it means for enterprise teams.

Some agencies still default to older approaches. Classic themes. Heavy page builders. Layered abstractions that make simple things harder than they should be.

That’s not always wrong, but it should always be a conscious choice.

A technically strong agency will be comfortable explaining where modern WordPress fits, where it does not, and why.

In practice, that usually means:

  • They treat the block editor as the foundation, not an add-on.
  • They understand block-based theming and where Full Site Editing is appropriate.
  • They create custom blocks when it adds value, not as a default.
  • They think about the editor experience as carefully as the front end.

If those points are missing from the conversation, that tells you something.

Code quality and engineering standards

You don’t need to read code to understand whether an agency takes engineering seriously.

You just need to listen to how they describe their work.

Teams with strong engineering practices tend to talk about process with confidence and specificity. They can explain how things are built, tested, and maintained without resorting to jargon or hand-waving.

Look for evidence of discipline.

Version control is standard. Code is reviewed. Deployments are structured, not manual. There is a clear approach to testing, even if it is pragmatic.

Just as importantly, they can connect those practices to outcomes.

Performance is considered from the start, not retrofitted. Accessibility is treated as a requirement, not an enhancement. Security is built in, not patched on.

If the answers feel vague or overly simplified, they probably are.

Questions to ask in a pitch or discovery meeting

You don’t need technical knowledge to ask effective questions. You just need to focus on how decisions are made.

A few well-placed questions can reveal a lot:

  • How do you decide what should be custom versus using existing WordPress functionality?
  • What does a well-architected WordPress project look like to you?
  • How do you approach performance from the start of a project?
  • What technical mistakes do you see most often in WordPress builds?
  • How do you ensure the site is maintainable over time?

Then listen carefully.

Strong agencies will talk about trade-offs. They will explain why, not just what. And they will connect technical decisions back to business outcomes without being prompted.

Personability and working relationship

Technical capability matters. But so does what it is like to actually work with the team.

Most enterprise WordPress projects are not short engagements. They involve ongoing collaboration, trade-offs, and moments where clarity matters more than speed. The relationship you have with the agency will shape that experience just as much as their technical decisions.

It is worth asking a simpler question alongside everything else: can you see yourself working closely with these people?

Trust is a useful proxy here.

Do they listen carefully to your brief and reflect it back with clarity? Do they explain their thinking in a way that makes sense, without defaulting to jargon? When something is complex, do they simplify it or hide behind it?

The strongest teams are able to translate technical decisions into clear, practical implications. They bring you into the process rather than keeping you at a distance.

There is also a more human dimension to consider.

Is the conversation easy, or does it feel strained? Do they challenge you constructively, or simply agree? Can they navigate ambiguity without creating confusion?

These signals matter because they compound over time.

A technically strong agency that communicates poorly can make a project feel difficult. A truly effective partner will make the process feel structured, collaborative, and, importantly, manageable.

That does not mean every interaction needs to be effortless. But it should feel like a working relationship you would be comfortable relying on.

Red flags to watch for

Some warning signs are easy to miss if you are not looking for them.

Over-reliance on page builders without a clear reason is one. So is solving simple problems with large numbers of plugins. Proprietary frameworks that lock you in should raise questions immediately.

Pay attention to tone as well as content.

If an agency dismisses WordPress core, avoids discussing the block editor, or struggles to explain their decisions in plain language, that is usually a signal of weak foundations.

Equally, if there is no clear story around updates, maintenance, or long-term ownership, you should assume it has not been thought through.

Making a confident decision

You don’t need to become an expert to evaluate one.

The best WordPress agencies are capable, but also intentional. They align with the platform, invest in good engineering practices, and build with the long term in mind.

Just as importantly, they can explain all of that clearly.

If you focus on those signals, you move the conversation away from surface-level comparisons and towards something more meaningful.

That is where the real differences are.

The post Evaluating the Technical Skills of a WordPress Agency appeared first on Human Made.

WordPress 7.0: Enterprise-Grade by Default

1 May 2026 at 13:09

After a couple of delays, WordPress 7.0 is scheduled to land on May 20th.

We’re looking at this through the lens of the beta releases and recent core updates, so some details may still shift. But the overall direction is already clear, and it’s one enterprise teams have been waiting for.

This is the release where WordPress starts to feel like it’s designed for how large organisations actually run.

A platform that’s catching up with how it’s used

Enterprise teams have been stretching WordPress to fit complex needs for years. Governance, consistency, performance, multi-team workflows, all solved through a mix of plugins, custom code, and process.

It works well, but it comes at a cost.

What’s happening in 7.0 is a gradual pullback of that complexity into core. The platform is starting to take responsibility for problems teams have been solving themselves for a long time.

That shift is where the real value is.

The editor finally behaves like a controlled environment

One of the most important changes in 7.0 is also one of the least visible.

The editor is now always iframed.

That brings a level of consistency that has been hard to guarantee across environments. Styles are properly isolated. What you see in the editor is far closer to what gets rendered on the front end, without unexpected bleed from themes or admin styles.

For teams running large platforms, this is a big step forward.

There is some cleanup involved. Older plugins and custom integrations that rely on direct access to the global document will need updating. But once that’s done, the editing experience becomes much more predictable.

And predictability is what scales.

Design systems start to hold their shape

Keeping content consistent across teams, regions, and brands is where things usually start to drift.

Building on the leaps forward in WordPress 6.9, WordPress 7.0 gives teams better tools to keep that under control without slowing anyone down.

Templates are clearer about what can and can’t be changed. Patterns are easier to treat as reusable, governed components. Block-level controls behave more reliably across different contexts.

All of that adds up to a system that reinforces the design system instead of relying on people to remember it.

For engineering teams, it means fewer edge cases and less defensive code. For content teams, it means fewer accidental breakages and a smoother path to publishing.

Governance gets simpler

If you’ve ever had to manage permissions and workflows across a large editorial team in WordPress, you’ll know how quickly things can get complicated.

Plugins help, but they also introduce more moving parts.

WordPress 7.0 improves the baseline here. Permissions are more flexible, ownership is clearer, and a lot of the common governance needs can be handled without reaching straight for additional tooling.

That doesn’t remove the need for custom workflows in complex organisations, but it does reduce how much of that logic sits outside core.

Fewer dependencies, fewer surprises when it comes time to upgrade.

Performance that keeps up with modern builds

Block-based sites are powerful, but they can get heavy fast.

7.0 includes improvements that target that complexity directly. Rendering is more efficient, assets are loaded more selectively, and caching behaves more consistently.

These are the kinds of changes that don’t always show up in screenshots but make a real difference in production.

For high-traffic platforms, it means more stable performance without as much ongoing tuning. For teams, it means less time chasing regressions and more time building.

Developer experience is moving in the right direction

There are a few updates in the recent developer notes that are worth paying attention to.

Block visibility tied to viewport opens up new ways to handle responsive behaviour directly in the editor. That changes how content models are designed and reduces reliance on front-end-only solutions.

Per-block custom CSS is also coming into play. Useful, but something teams will want to manage carefully to avoid introducing inconsistency at scale.

The common thread is that more capability is moving into the block layer. That’s powerful, but it also means teams need to think more deliberately about how they govern it.

A better fit for modern architectures

Most enterprise platforms aren’t running WordPress in isolation.

They’re integrating with front-end frameworks, personalisation tools, analytics platforms, and more. In that world, consistency in data and APIs is essential.

7.0 continues to make progress here. Block data is easier to work with, API responses are more predictable, and the gap between what editors create and what developers consume keeps getting smaller.

For headless and hybrid setups, that reduces friction across the board.

WordPress 7.0: What to look at before May 20th

With the release just around the corner, now is the time to start testing.

A few areas worth focusing on:

  • Editor integrations
    Check anything that interacts directly with the editor environment, especially where it touches the DOM.
  • Design system enforcement
    Look at how templates and patterns are used today and where core features can take over.
  • Permissions and workflows
    Review your governance model and see what can be simplified.
  • Performance on complex pages
    Test the pages that tend to cause problems and see how they behave on the latest beta.
  • Plugin compatibility
    Pay close attention to plugins that interact with the admin or editor experience.

Where this leaves enterprise WordPress

WordPress has been running enterprise platforms for a long time. What’s changing with WordPress 7.0 is how much effort it takes to keep things running well.

More of the patterns that teams have built around WordPress are now becoming part of the platform itself. That reduces duplication, lowers maintenance overhead, and makes upgrades less of a balancing act.

There’s still work to do, especially for platforms with a lot of legacy customisation. But once that alignment is in place, the payoff is a system that’s easier to manage and more predictable over time.

That’s a meaningful step forward.

The post WordPress 7.0: Enterprise-Grade by Default appeared first on Human Made.

Why enterprise brands are backing WordPress in 2026

19 March 2026 at 15:15

Our recent event, WP:26, was a deep dive into the future—and I was completely fired up to see us gather technologists, publishers, and platform leaders to explore the key patterns shaping WordPress in 2026 and beyond. We packed an afternoon full of talks and discussions, covering the massive impact of AI, accessibility, enterprise publishing, and evolving web standards on the essential role of a CMS.

To cap off a day of critical insight and conversation, we hosted a truly amazing final panel discussion, ‘Why we’re backing WordPress in 2026’, with an exceptional line-up of speakers.

Although Executive Director of WordPress, Mary Hubbard, was unable to attend live, she was kind enough to provide a video intro to kick us off:

“The question isn’t just which CMS should we use; it’s ‘which platform can and will evolve with us?’ WordPress’ enduring strength is its ability to adapt to changing demands and evolving organisational needs… What really sustains the platform is the ecosystem around it, the community, the contributors, and the organisations pushing it forward in production every day.” – Mary Hubbard, Executive Director, WordPress

The panel consisted of:

Meeting the challenges of enterprise publishing

The core of our discussion centred on how and why enterprise brands are actively choosing and investing in WordPress as their platform of the future. The conversation was grounded in the reality of the challenges faced by media companies in 2026—from managing content at a massive international scale to navigating a rapidly shifting technological landscape.

We heard first-hand accounts of how WordPress enables huge international publishing brands to meet these challenges. The consensus was clear: the platform’s adaptability, open nature, and robust ecosystem are its greatest assets when faced with the demands of an enterprise environment.As Gabriel Koen, SVP, Technology at PMC, noted:

“WordPress does a great job of staying modern… the fact that we’ve been able to build on top of it for almost two decades and still see it as the platform for the next several years is pretty remarkable.” Gabriel Koen, SVP, Technology, PMC

From Drupal to WordPress: The CERN example

One of the most compelling threads of the discussion—and something that really excited me—was the story of CERN, the birthplace of the world wide web, and their decision to embrace WordPress after moving from Drupal.

Joachim Valdemar Yde, Web Manager at CERN, provided amazing insight into how one of the world’s most significant scientific organisations chose to standardise on WordPress after a year-long, 14-requirement evaluation against alternatives like Wix and Squarespace. He stressed the importance of having a system that allows their users—scientists and researchers—to be content creators, not web developers.

The move by an organisation like CERN highlights a major shift: WordPress is no longer just a blogging tool, but a flexible, scalable, and future-proof enterprise platform ready for the next generation of web challenges.

Enterprise-grade solutions for what’s to come

The panel also addressed the essential role of enterprise-grade solutions and partnerships in preparing brands for the future. Steph Yiu noted a surge in new enterprise interest driven by AI, which I think is a really important shift:

“AI is forcing innovation across every business… We want to build on a future-proof platform. Closed just isn’t going to cut it for me anymore. I want to build on an open stack.” – Steph Yiu, CEO of WordPress VIP

This perspective underscored that enterprise adoption isn’t just about the open-source software itself, but also the world-class hosting, support, and strategic development partners that turn a flexible CMS into a mission-critical business platform. It’s the combination of the open-source core and the mature, robust ecosystem that provides true peace of mind for global brands.

The conversation also touched on the critical transition of AI from experimentation to production. Gabriel discussed using AI behind the scenes for content translation and processing vast print archives, while Umer shared News UK’s focus on leveraging AI to streamline print and digital publishing workflows to “take entire swathes of effort out of your business.”

If you want to make a dent with AI, you have to take entire swathes of effort out of your business and I think that’s really where the fundamentals are for us at the moment. We’re still a print business and it’s a huge part of our revenue stream, although it’s sort of counter to the WordPress ethos, WordPress is where we do all of our authoring for our print content or certainly where we want to move all of our authoring for our print content alongside our digital content. So, a big part of what we’re working on at the moment is how we streamline workflows. – Umer Ehsan, Director of Technology – Content, News UK

The Future-Proof Platform for Enterprise

If there was one idea that framed the end of WP:26, it was this:

WordPress is the definitive, future-proof platform for the enterprise web.

The final panel discussion reinforced the core message of the day: WordPress is evolving, driven by an open community and backed by the world’s largest digital brands. The platform’s ability to evolve, adapt to modern challenges (be it AI, headless architecture, or new publishing models), and maintain a stable core is why we—and so many others—are backing it for 2026 and beyond.

The collective backing of the panelists, from the platform’s governing body to global publishing and scientific institutions, offers an undeniable picture of its long-term viability and central role in the future of the web.

For me, this event was a tremendous success. We dove deep into the patterns shaping WordPress, and I’m immensely proud that we’ve once again brought together such a vibrant, community-driven event. My sincere thanks go to our incredible panel—Gabriel, Umer, Joachim, and Steph—for generously sharing their time and such critical insights with us. It’s the passion and commitment of people like them that truly sustains the platform and continues to push us forward in production every single day. I couldn’t be more hyped about what we’ll achieve together in the years to come.

Ready to explore all the insights and research from WP:26? Access the full WP:26 Event Replay page here and download our supporting market analysis report, ‘WordPress in 2026: The dawn of the intelligent CMS’.

The post Why enterprise brands are backing WordPress in 2026 appeared first on Human Made.

❌
❌