Paxform platform

Paxform is the venture where the two halves of the practice stop being separate engagements. It is a forms and workflow automation platform — which is to say, it is twenty years of watching organisations rebuild the same form logic badly, turned into a product.

Wearing both hats

Design direction and product ownership on the same product is an uncomfortable combination, and a clarifying one. The design argument and the sequencing argument happen in the same head, which removes the usual escape route of blaming the roadmap for the compromise.

• Design direction — the product’s visual and interaction language, and the component library that makes it repeatable.
• Backlog ownership — writing the stories, sequencing them, and saying no to the feature that would have quietly broken the model.
• Shipped releases — the part that distinguishes a product from a prototype.

Where the token pipeline gets tested

The three-tier DTCG token architecture described on the home page is not a theoretical position. Paxform is where it has to survive contact with a real component library, real engineers, and a release cadence that does not pause for a ramp change.

A design system that cannot ship a colour change as a commit is a document, not a system.