Go Develop Practical software engineering for UK businesses.

Go Develop

Practical software engineering for UK businesses.

Latest Articles

Who Changed What, and Can You Prove It? Building Audit History That Inspectors Can Read
Digital Transformation

Who Changed What, and Can You Prove It? Building Audit History That Inspectors Can Read

A database log table records technical events; an audit trail answers human questions. For UK products in regulated or accountable settings, change history should be a customer-facing assurance feature with clear actors, reasons, retention and export. This article explains how to design it properly.

The Devolved Detail: Designing One UK Product for Four Nations
Accessibility

The Devolved Detail: Designing One UK Product for Four Nations

The UK is one market with four legal and linguistic realities. Building for England, Scotland, Wales and Northern Ireland does not require four products, but it does require deliberate decisions about language, law, formats and content governance. This guide explains where local difference deserves product logic.

The Museum of Old Decisions: Rebuilding UK Software Without Rebuilding the Past
Product Engineering

The Museum of Old Decisions: Rebuilding UK Software Without Rebuilding the Past

A legacy system is less a product than a museum of old decisions. When UK SMEs replace one, feature parity can preserve workarounds, abandoned policy and hidden cost. This article sets out how to rebuild around outcomes, sequence continuity deliberately and retire clutter with confidence.

Paid Once, Recorded Once: Engineering Payment Flows That Withstand Repetition
Product Engineering

Paid Once, Recorded Once: Engineering Payment Flows That Withstand Repetition

Payment failures rarely announce themselves dramatically. More often they arrive as a duplicate webhook, a refreshed checkout page or a confirmation that lands after support has already refunded by hand. This article sets out how UK product teams can design payment flows that expect repetition, prove what happened, and give finance a ledger they can defend.

The Day After the Expert Leaves: Designing Continuity Into UK Business Software
Product Engineering

The Day After the Expert Leaves: Designing Continuity Into UK Business Software

Staff turnover is normal, but software that depends on one knowledgeable individual is not. This article sets out how UK SMEs can treat continuity as a product requirement, using role-based permissions, visible ownership and decision-rich audit trails to keep work moving when the expert moves on.

Reading the Queue: How UK SMEs Can Turn Support Logs into Product Evidence
Product Engineering

Reading the Queue: How UK SMEs Can Turn Support Logs into Product Evidence

Support tickets are often treated as operational noise, yet they contain some of the clearest evidence of where a product fails its users. This article sets out a practical method for UK SME teams to classify root causes, separate defects from design gaps, and use a monthly review to inform product decisions without overfitting to the loudest voice.

Data Flows Are Architecture: Building UK–EU Transfers That Outlast an Adequacy Review
Product Engineering

Data Flows Are Architecture: Building UK–EU Transfers That Outlast an Adequacy Review

Adequacy decisions are reviewed, extended and occasionally questioned, yet the code that moves personal data across borders seldom changes with them. This article sets out a practical engineering approach to UK–EU transfers: a flow-level register, residency enforced at build time, transfer logging as a product capability, and exit rehearsals with vendors before policy forces the issue.

The Confidence Budget: Reading Software Estimates as Risk Documents
Procurement

The Confidence Budget: Reading Software Estimates as Risk Documents

A single-point software estimate is often treated as a promise, yet it is better understood as a compressed statement of uncertainty. This article explains how UK buyers can read ranges, assumptions and confidence levels as practical decision tools, compare proposals on equal terms and avoid the false precision that undermines trust before a build begins.

Common Core, Local Flavour: Engineering a Franchise Platform That Scales Without Drift
Product Engineering

Common Core, Local Flavour: Engineering a Franchise Platform That Scales Without Drift

Franchise software often fails at the same point: head office needs comparable data and brand control, while local operators need enough autonomy to run their sites. This article sets out the engineering choices behind a franchise-ready platform, from tenant hierarchies and territorial permissions to local pricing overrides and repeatable site onboarding.

Entities Are Not Strings: Designing UK Business Onboarding That Knows What It Is Looking At
Product Engineering

Entities Are Not Strings: Designing UK Business Onboarding That Knows What It Is Looking At

UK B2B sign-up forms often treat a legal entity as two text fields: a company name and a VAT number. That works until a sole trader, a charity or an overseas-owned UK company arrives. This article sets out a practical data model and validation strategy using Companies House, VAT and PAYE signals, with clear rules for when to block, when to review and when to let a legitimate edge case through.

The Art of Taking Things Away: A Deprecation Playbook for UK Product Teams
Product Engineering

The Art of Taking Things Away: A Deprecation Playbook for UK Product Teams

Most UK software products are better at adding features than removing them. A credible deprecation process — grounded in usage evidence, clear notice periods, data export and sensible communication — protects customers, reduces operational drag and strengthens the product's commercial story.

Blackspots, Basements and Stone Walls: Engineering Field Software That Keeps Working
Product Engineering

Blackspots, Basements and Stone Walls: Engineering Field Software That Keeps Working

Field teams in the UK often work where connectivity is optional, intermittent or misleading. This article sets out a practical offline-first approach for product teams, covering local-first storage, sync conflict policy, honest interface behaviour and a testing regime that does not rely on a hopeful journey on the train.

The Messy Prospect Test: Why a Hostile Demo Dataset Belongs in Your Product
Product Engineering

The Messy Prospect Test: Why a Hostile Demo Dataset Belongs in Your Product

Most software demonstrations are rehearsed against a sandbox so tidy that no real UK customer could ever resemble it. A deliberately awkward demo dataset turns those first messy accounts from a support risk into a commercial asset, provided it is built and governed as part of the product.

Proof, Not Promises: Turning Restore Drills into Assurance for UK SMEs
Digital Transformation

Proof, Not Promises: Turning Restore Drills into Assurance for UK SMEs

A backup policy tells you what should happen after data loss. A restore drill proves what will happen. For UK SMEs facing insurer questionnaires, client assurance requests and auditor scrutiny, the difference matters. This article sets out a practical quarterly programme for testing recovery and recording the evidence.

Clocks With Consequences: Treating UK Statutory Deadlines as Core Product Logic
Product Engineering

Clocks With Consequences: Treating UK Statutory Deadlines as Core Product Logic

Statutory deadlines are not calendar reminders; they are legal obligations with evidence requirements, extensions and awkward calendar rules. This article explains how UK product teams can model deadlines as first-class domain objects, keep an audit trail and test the cases where a normal working day is anything but normal.

Room to Breathe: Building a UK Release Calendar That Respects the Trading Year
Product Engineering

Room to Breathe: Building a UK Release Calendar That Respects the Trading Year

Most UK teams treat the December change freeze as an emergency measure announced three weeks too late. It is better understood as a product constraint you can schedule twelve months in advance. This guide sets out how to map deployments around trading peaks, the tax year, bank holidays and annual leave, and how to run a lightweight change-advisory route that still lets genuine fixes through.

Designing for Forgetting: Making Data Erasure a Product Feature, Not a Support Ticket
Product Engineering

Designing for Forgetting: Making Data Erasure a Product Feature, Not a Support Ticket

Erasure requests are usually handled as legal admin, which means every request becomes an engineering incident. This article sets out how UK product teams can map personal data, build deletion and export workflows, manage backups and processors, and keep an audit trail — turning a statutory obligation into a routine, well-designed operation.

Beyond the Postcode Box: Designing UK Address Capture That Holds Up in the Real World
Product Engineering

Beyond the Postcode Box: Designing UK Address Capture That Holds Up in the Real World

UK addresses resist tidy assumptions: one postcode can serve several towns, a flat may have no number, and a BFPO line obeys its own rules. This guide sets out how product teams should design address capture that converts, validates sensibly and stores data fit for purpose.

The Screen Nobody Designed: Auditing Error States Before They Cost You Customers
Product Engineering

The Screen Nobody Designed: Auditing Error States Before They Cost You Customers

Most product teams design for the path where everything works. The path where it does not is where customers are won or lost. This guide sets out a repeatable audit for error, empty and edge states, and a way to rank the fixes by commercial impact.

The Rate Will Move: Designing UK Billing Software for Tax Change
Product Engineering

The Rate Will Move: Designing UK Billing Software for Tax Change

VAT rates and invoice rules are policy, not constants. This article explains how UK SMEs can model tax as versioned configuration with effective dates, audit trails and testable boundaries, so a future change does not become a rebuild.