Product & Delivery blogs
Featured blogs
Generated image: Villar David editorial
Blogs
Product & Delivery
Posts filed under Product & Delivery. View every category.
2026
Updating a procedure after a workaround
Coding agents are running for longer and reading more context before they return. That makes the current procedure more important because an agent can follow an old workaround much further before anyone notices.
Build the searchable specification before the application gets expensive
When requirements are scattered across PDFs, email and meeting notes, implementation starts by repeatedly rediscovering the product. Consolidate the source material into a searchable specification and keep each decision linked to the evidence behind it.
Reconciling portals, permissions and integrations before release
In a multi-portal product, the final release checks often fail between components: one role sees the wrong state, an integration updates late or two screens apply different rules. The examples in this post are a composite of recurring delivery problems.
2024
Paid modules change more than the checkout screen
Adding paid access to a learning platform touches enrolment, permissions, account state, completion records, certificates and support. I am breaking the work into those consequences because a clean payment screen does not help if the learner receives the wrong access or the records disagree afterwards.
The workflow that starts when a payment clears
Recording a successful payment is only one part of the job. The surrounding workflow has to update the right account, send the right message, avoid duplicate handling and leave enough state for support staff to work out what happened when one step fails.
Start with the work people are already doing
AI workflows built from the documented procedure usually miss how the job is done. I watch the handoffs and workarounds first, especially where people leave the official system to finish the task.
Why I’m writing this down
I keep notes while I work, usually because a decision will need explaining again months later. This journal is where I will keep the implementation details, failures and changes of mind that are worth returning to.