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 longer and reading more context before they come back, so an out-of-date procedure matters more now. An agent can follow an old workaround a long way before anyone notices.
Build the searchable specification before the application gets expensive
When requirements are spread across PDFs, email and meeting notes, every piece of implementation starts with rediscovering the product. I'd pull 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 last release checks tend to fail in the gaps between components: a role sees the wrong state, an integration updates late or two screens apply different rules. The examples here are a composite of problems that keep coming up in delivery.
2024
Paid modules change more than the checkout screen
Adding paid access to a learning platform touches enrolment, permissions, completion records, certificates and support. I'd work through those before polishing checkout, because a clean payment page doesn't help much if the learner ends up with the wrong access.
The workflow that starts when a payment clears
When a payment clears, I want the right account updated, one message sent instead of three, and enough left behind that support can work out what happened if a later step fails.
Start with the work people are already doing
If you build an AI workflow from the documented procedure, you'll usually miss how the job actually gets done. I'd watch the handoffs and workarounds first, especially the spots where people leave the official system to finish the task.
Why I’m writing this down
I keep notes while I work, mostly because I'll have to explain a decision again months later. This journal is where I'll put the implementation details, failures and changes of mind I think are worth coming back to.