Every piece of content on this page is written by a named Axiant practitioner. No anonymous posts. No agency-written content. What you read here comes from people who run the engagements.
The content is organized by author voice and topic. Each voice has a distinct lane: operational and philosophical, technical and implementation-focused, and executive and capital-disciplined. Use the filters below to find what is most relevant to your role and situation.
Before exploring the full archive, this post is the structural foundation. It explains the five root causes behind most automation failures, introduces the DRIFT framework, and sets the context for everything else published here.
Business process automation promises faster operations, lower costs, and fewer errors, but only when applied to processes that are ready for it. This guide covers the full BPA landscape: technologies, use cases, and the principles that separate leverage from scaled dysfunction.
No posts are currently published. New content will appear here as it is released.
Each author writes from a distinct perspective built on a distinct role. The voice differences are intentional. They reflect how three different buyer personas experience the same problem from three different vantage points.
Curtis writes about how PFA works in practice: the mechanics of Shadow Process mapping, the Automation Decision framework, Process Readiness Score application, and the technical architecture of Visible Systems. His content is for IT Directors and technical leads who need to understand the implementation specifics.
Jeff writes about why the automation industry's approach is structurally broken and what the right sequence looks like. His content is the operational and philosophical voice of the methodology: DRIFT analysis, Automation Reflex diagnosis, and the process-first argument made in practitioner language.
Thomas writes about automation as a capital discipline issue. His content is for CEOs and CFOs who are accountable for the ROI of automation investments. He frames the 88% Problem as a board-level risk, connects automation outcomes to driver accountability, and builds the executive case for the process-first approach.
The Axiant newsletter delivers new Insights posts as they are published. The cadence is tied to publishing, not to a schedule. When a practitioner finishes a post that meets the publication standard, it goes out. No weekly round-ups. No promotional content. Just the post.
The archive of past newsletters is available on the newsletter page. Every issue links to the posts it contains.
One issue per month. No filler, no vendor hype — just data, analysis, and the practitioner perspective.
Subscribe to the DRIFT ReportNo spam. No third-party sharing. Unsubscribe anytime.
Every post published on this page has been written or substantively reviewed by the named practitioner author. No post is published from outside the Axiant practitioner team. No post is published that makes claims not grounded in engagement data or cited research. The byline is a commitment, not a decoration.
This standard exists because the buyers who read this content are making real decisions with real consequences. They deserve content from people who have done the work, not content produced to rank in search.
Reading about DRIFT, the Four Paths, and the PFA Loop is a useful starting point. The next step is understanding which elements are present in your organization and what the right sequence looks like for your highest-priority processes. That is what the PFA Diagnostic produces.
12 questions. Scored output across all five DRIFT dimensions. Find out exactly which root causes are present in your organization before your next initiative launches.
Start the assessmentThe six-stage PFA Loop, the Four Paths framework, and the accountability architecture that makes every engagement measurable. The methodology behind the content.
Explore the methodologyEvery case study follows the same structure: before-state, DRIFT diagnosis, Four Paths decision, and quantified after-state. The documented record of the methodology producing results.
See the proof