Fractional CXO
Elegant service architecture follows consistent structural logic regardless of domain. A verification flow that builds trust progressively works for the same fundamental reasons whether it’s banking or healthcare. The surface details change, the underlying principles don’t.
Cross-domain pattern recognition reveals these principles. I work across fintech, healthtech, government infrastructure, pharmaceutical AI and emerging technologies—each project adds to what I can see. This means designing from structural insight rather than sector conventions.
Fractional engagement gives you episodic access to strategic capability when transformation requires it, without permanent overhead.
How transformation works
A financial platform needed extensive KYC verification for regulatory compliance. Standard implementation had users provide all identity documentation upfront before accessing any functionality. Conversion was low but everyone assumed regulatory requirements constrained the architecture.
The structural opportunity was in sequence, not compliance. What if users could experience service value before deciding to invest personal information? Limited functionality first, demonstrating what the platform offered. Verification required only when users chose to expand their engagement.
Same regulatory compliance. Completely different relationship between what the service demanded and what it delivered. Users now built trust through experience rather than being asked for it upfront. Completion rates increased 340%.
This reveals something about transformation. The technical execution was already competent. What changed was the fundamental architecture—the sequence in which value and trust developed, the relationship between access and disclosure.
Pattern recognition means seeing these structural opportunities quickly. The same logic that made progressive trust work in fintech applies across healthcare onboarding, government service delivery, platform activation. Once you see the pattern, you can design from principle.
What you get
Episodic access to diagnostic thinking and strategic redesign. Typical engagement runs 6-12 weeks: analysis of your service architecture, identification of structural opportunities, redesign that creates the transformation you’re seeking. Your teams then execute using their existing capabilities.
Time commitment varies by complexity—generally 2-3 days per week during diagnostic and design phases. You bring in this capability when designing new services, when you’re seeking step-change improvements, or when you need insights that operate across experiential and transactional dimensions.
Projects have included pandemic infrastructure for GOV.UK serving 47 million users, transformation work with Pfizer, innovation for BBC and American Express. Work spans traditional and emerging sectors: healthtech, fintech, government digital services, decentralised systems.
My background is narrative design from Royal College of Art—understanding how people move through space, how sequences create meaning, how experience unfolds. This cross-disciplinary foundation turns out to be precisely what structural design of digital services requires. You can read more about this approach at nakedinstinct.xyz, including pieces on AI and spatial experience and architecting pandemic infrastructure.
Let’s talk
Initial conversation typically runs 30 minutes. We’ll explore what you’re looking to transform and whether structural redesign creates the outcomes you’re seeking.