Akiba One – Fintech + Regulatory Compliance App Case Study

Mapping the Decision Engine

One of the most important parts of the project was redesigning the platform’s workflow automation engine.

Before designing the interface, I mapped the platform’s core operational logic into four foundational building blocks:

Triggers

Events that initiate workflows.

Rules

Conditional logic that evaluates scenarios.

API Integrations

External data checks and financial signals.

Actions

Automated outcomes based on logic decisions.

The challenge was translating highly technical backend logic into a visual mental model that operational teams could instantly understand.

I transformed these abstract concepts into modular visual blocks that users could arrange and connect naturally.

This dramatically reduced the learning curve for non-technical teams.

Post-Development UX Audit

One thing I strongly believe is that design does not end at Figma handoff.

After the engineering team implemented the Workflow Builder, I conducted a detailed post-development UX audit to ensure:

• Interaction consistency
• Usability quality
• Edge-case handling
• Implementation accuracy

This helped identify:

• Interaction mismatches
• Visual inconsistencies
• Spacing issues
• Uability gaps before broader rollout

For enterprise SaaS products, these small details matter enormously because users interact with the platform daily for operational decision-making.

Designing the Workflow Automation Builder

The Workflow Builder became the centerpiece of the AkibaOne experience.

I designed a node-based visual interface that allowed users to create complex decision trees through drag-and-drop interactions on a clean dot-grid canvas.

The experience focused heavily on clarity and reducing cognitive load.

Reducing Cognitive Load

Instead of forcing users to interpret technical terminology, I introduced contextual micro-labels directly above workflow nodes.

Examples included:

• “Starts when”
• “Check if/else.”
• “Do this”

These small UX decisions dramatically improved scanability and helped users immediately understand the purpose of each block before reading deeper details.

Visual Branching & Flow Clarity

Financial workflows often contain complicated branching scenarios.

For example:

• If KYC passes → continue
• If KYC fails → reject
• If the fraud score is high → manual review
• If API fails → retry verification

I designed the branching system so users could visually understand these paths without feeling overwhelmed.

The interface handled:

• Conditional logic
• Branching outcomes
• API sequencing
• Action routing is intuitive and visually organized rather than technically intimidating.

Searchable Actions Panel

To improve workflow construction speed, I designed a searchable right-side actions panel where users could quickly:

• Add nodes
• Search integrations
• Configure actions
• Expand workflows dynamically

This reduced friction during workflow creation and improved discoverability across the platform.

Video Walkthrough & Product Communication

To help stakeholders fully understand the workflow builder, I also created and edited a complete product walkthrough video with voiceover narration.

The video demonstrated:

• Workflow creation
• Node configuration
• Branching logic
• Testing environments
• Workflow publishing

This became an important communication asset for explaining complex functionality in a much more digestible way.

Designing the Passport Verification Experience

Alongside the enterprise workflows, I also designed the consumer-facing passport verification flow.

KYC experiences are naturally high-friction because users are asked to:

• capture documents,
• position IDs correctly,
• deal with camera permissions,
• and trust the platform with sensitive data.

My goal was to make the experience feel guided and reassuring.

Real-Time Guidance

I designed the camera interface with:

• Dynamic document boundaries
• Real-time visual feedback
• Alignment assistance
• “Hold still” prompts

When the passport was aligned correctly, the bounding box turned green to reassure users that the system had successfully recognized the document.

This reduced uncertainty and improved capture quality.

Confidence Before Submission

I also introduced a dedicated review screen that allows users to inspect their image before submission.

This included:

• Image previews
• retake functionality
• Confirmation feedback

This small UX improvement helped reduce:

• User frustration
• API failures
• Failed OCR scans

Results & Impact

The redesign transformed AkibaOne from a technically dense operational system into a scalable enterprise fintech platform with significantly improved usability and workflow clarity.

Key Outcomes

Improved Operational Efficiency

Non-technical teams could independently create and manage decision workflows without relying heavily on developers.

Reduced Cognitive Complexity

Visual workflows and modular logic blocks made complex financial automation easier to understand.

Stronger Risk Mitigation

The testing environment reduced deployment risks and improved workflow reliability.

Better Platform Consistency

The design system established a scalable foundation across the entire product ecosystem.

Faster Engineering Execution

Reusable components and structured UI patterns accelerated development velocity and reduced UI inconsistencies.

Reflection

This project pushed me far beyond traditional UI design.

It required:

• Systems thinking
• Enterprise UX strategy
• Workflow architecture
• Cognitive load reduction
• A deep understanding of operational fintech environments.

Working directly with Akiba Digital gave me the opportunity to design for real-world financial workflows where usability directly impacts operational efficiency and trust.

The biggest lesson from this project was simple:

1. Complex systems do not need to feel complicated
2. With the right UX architecture, even highly technical financial workflows can become understandable, approachable, and scalable