THE WGMI JOURNAL

Better systems.
More room to grow.

Notes on better websites, connected systems, and the everyday work between them.

Engineering in plain English

WGMI asks A product or a project? Three checks cover the everyday job, the specific rule and the ongoing work, to help compare a product, a connection or a specific build.

Engineering in plain English16 Oct 2026

A product or a project? Compare the job before the tools

Compare an existing product, a connection between tools and a specific build using one recurring job, one essential rule and a plan for ongoing ownership.

WGMI4 min read

WGMI note about DOLFA, clearly labelled in development. Four questions define an illustrative pilot: workflow, participants, test data and stop condition.

Engineering in plain English14 Oct 2026

Give your pilot a boundary before it starts

DOLFA's development plan opens a practical question for any proposed pilot: which workflow, people and test material are in scope, and when will you pause?

WGMI4 min read

WGMI working note from the Taoro project. An illustrative client update shows a service page draft, its review stage and a request to confirm the service wording. A note says that a shared view is not an approval action.

Engineering in plain English13 Oct 2026

Design the client view on purpose

A design choice in Taoro offers a practical way to choose what clients see, explain the next decision and inspect a project view before sharing it.

WGMI4 min read

Engineering in plain English6 Oct 2026

A second click needs a rule

Define what counts as a repeated request, what signals new intent and who checks an uncertain result. A filled rule note for an imagined repair process.

WGMI4 min read

WGMI Journal. One field, one owner. Decide where a change begins. Example field: Opening hours. Meaning: Which hours are these? Owner: Who approves a change? Record: Where is it updated?

Engineering in plain English5 Oct 2026

One field, one owner: agree which record to trust

When two tools disagree, give your team a record to check and a person who can confirm the value. A practical note for one shared field.

WGMI4 min read

WGMI Journal. Start with three things. The problem, your setup and a useful result.

Engineering in plain English2 Oct 2026

How to write a useful first project brief

Use a filled example to describe the problem, the users, your setup and the result you want, with clear limits and questions still to answer.

WGMI4 min read

WGMI Journal. Build around what works. Your setup: What stays? Our part: What do we build? The handover: What does your team need?

Engineering in plain English1 Oct 2026

Build around what already works

Define what stays, what changes and what your team needs at handover. A practical scope note for adding to an existing system.

WGMI4 min read

Engineering in plain English30 Sept 2026

Before you call it done: the walkthrough to ask for

Before signing off a first release, ask for a walkthrough your team can repeat: the main task, what happens when it fails, and the handover that lets the team run it.

WGMI1 min read

Engineering in plain English28 Sept 2026

Choose the next useful improvement before you build

Describe the task, the current setup and a useful result. A practical way to decide where a website, software or systems project should begin.

WGMI4 min read