Insights

Writing on complex product design.

Articles on product design, UX architecture, design systems, and complex enterprise systems - organized by persona and topic, drawn from real projects.

20 articles

BlackSwan

Engineering LeadersDesign Systems

A Design System That Earns Its Keep in a Risk Platform

A design system on a banking risk platform isn't about pretty buttons. It's a contract between design and engineering. On BlackSwan, one shared library powered five surfaces — triage, entity mapping, dashboard, horizon scanning, the risk engine — built solo. The win for the CTO: change a threshold display once, it propagates everywhere, and it's defensible in an audit. Consistency without coordination overhead is the cheapest velocity you'll ever buy.

Read

BlackSwan

Studio & Agency

FinTech Expertise as Part of Your Existing Team: A Plug-and-Play Solution for Core Systems

Studio leaders, a complex FinTech or cyber project just landed on your desk and you don't have a free senior who knows the domain? Instead of panicking or hiring, you can work on a Contractor model. That's exactly how I joined BlackSwan's Risk Engine project — zero growing pains, maximum expertise from day one.

Read

BlackSwan

FoundersColor & Psychology

Color That Signals Trust, Not Alarm

Selling risk software to banks? Your product has three seconds to feel credible — and color is doing that work before anyone reads a word. On BlackSwan I refused to drown the UI in red. If every flag screams danger, severity means nothing. A calm, calibrated palette tells a buyer the tool is in control of the situation. In compliance, that composure IS the pitch.

Read

BlackSwan

Product ManagersMicro-interactions & Animation

Motion as Feedback in a Real-Time Risk Engine

On BlackSwan's Risk Engine, admins tune module weights and sanctions thresholds — decisions with real consequences. I rebuilt it from nested forms into a real-time system, and micro-interactions are what make 'real-time' felt, not just claimed. Every adjustment shows its effect as you make it. For a PM: functional motion reduces uncertainty and errors. The best animation isn't dazzle — it's the system saying 'I heard you.'

Read

BlackSwan

Project Managers

Risk Management in UX Definition: How Do You Prevent Scope Creep in a Complex System?

Project managers (PMOs), you know the feeling when UX design jams up your Delivery? It happens because teams race to pixels before locking the logic. On the BlackSwan project we did it the other way around: first we locked the flow architecture, and only then did we design. The result: zero Scope Creep and precise delivery against launch targets.

Read

BlackSwan

Engineering LeadersR&D Collaboration

Designing the Risk Engine With R&D, Not At Them

"Real-time and auditable" aren't UI words — they're promises the backend has to keep. On BlackSwan's Risk Engine I brought those constraints to R&D before locking the design, not after. The cheapest place to hear "that's expensive" is a whiteboard. Design with engineering's constraints, not around them.

Read

BlackSwan

Engineering LeadersProject-Specific Data Visualization

Visualizing Entity Relationships Without Drowning the User

BlackSwan asks opposite things of data viz: investigators need dense entity-relationship and ownership structure made legible; analysts need condensed triage they can clear fast. Same data, opposite goals. A naive node-graph dump is unreadable — the viz layer has to be opinionated about what to surface vs. defer to drill-down. For a CTO: these aren't bolt-on charts. They're purpose-built to the domain's data shapes. That specificity is what users trust under real caseloads.

Read

BlackSwan

Project ManagersDocumentation & Organizational Handoff

Documenting BlackSwan So It Outlived the Solo Designer

Solo designer on a five-surface platform = a single point of failure for everything the product knows about its own design. So I documented the why, not just the what — especially for the Risk Engine, where the rationale behind each rule protects the audit trail. Documentation isn't overhead; it's continuity insurance. The org should own the knowledge, not your head.

Read

BlackSwan

Product Managers

Information Architecture in Data-Heavy Systems: How Do You Prevent Cognitive Overload in Analysis?

Product managers, stop overloading your dashboard. Analysts are human beings, not machines. In designing BlackSwan's Risk Engine, we proved that Progressive Disclosure of data prevents cognitive overload and cuts decision-making time by 40%. Less is more, especially in FinTech.

Read

BlackSwan

Founders

From Initial Concept to a FinTech Product (Risk Engine) That Raises Capital and Wins Investors

Founders, you've got an insane algorithm in the backend but a demo that looks like the 1990s? Investors buy with their eyes. At BlackSwan we turned complex financial logic into a breathtaking visual interface that helped convey the company's value in the pitch. Don't let bad UX kill your raise.

Read

BlackSwan

Project ManagersDelivery & Handoff to Development

A Handoff That Didn't Generate a Second Backlog

A weak handoff creates a second, invisible backlog: clarification threads, mismatched components, "is this final?" pings. On BlackSwan I leaned on the Design System so five surfaces shared real components, not five interpretations. Handoff isn't a moment you throw files over a wall — it's a system that keeps the build moving without you in every thread.

Read

BlackSwan

Project ManagersUsability Testing

Testing the Risk Engine Before It Cost Us a Sprint

The most dangerous task in a plan is the one everyone assumes is simple. On BlackSwan that was the Risk Engine config. We usability-tested it as clickable flows before a line of production code existed. Test your highest-uncertainty surface first — that's where findings still have room to change the schedule instead of blowing it.

Read