Skip to content
Alan Lindsay ConsultingEmail

Design and build

Design it and build it

Design

Interfaces for complex, high-stakes work, and the systems behind them.

I design for places where a confusing screen has a real cost: fraud investigation, identity checks, enrollment at scale. The work covers research, information hierarchy, and engineering-ready designs that account for the edge cases.

Where many teams share one product surface, I build the design system that keeps them consistent.

Engagements are scoped as statements of work.

You might need this if…

  • A confusing screen costs you missed cases, bad decisions, or support tickets.
  • Several teams build on one product and it no longer looks like one product.
  • People rely on training or workarounds to finish a core task.

Selected examples

  • Experian. Led the global design system across more than 40 product teams and 70 applications, and designed fraud and identity tools whose decision-first layout roughly tripled case throughput.

    He led the creation of the fraud and identity design system, partnering with engineers on usable component libraries.

    Matthew SolisSenior Product Designer, Google Workspace · Via Experian

  • Circadence. Redesigned the cybersecurity training experience from scratch.

  • The 41st Parameter. Engineered the frontend of a high-volume fraud and identity platform, partnering with risk specialists so the fraud logic stayed accurate on screen and dashboards over datasets of 100,000 records stayed responsive for analysts.

    Alan strives for holistic approaches in requirements, design, execution, and delivery, always with the users in mind.

    Ries van ZoestData science and risk management · Via The 41st Parameter and Experian

  • OneShare Health. Overhauled the enrollment, producer, and internal tools so throughput grew without adding support staff.

Development

A scoped build, delivered to production and handed over.

When the recommendation is to build, I build it: architecture, implementation, and the hardening that gets it into production.

Each build is its own statement of work with a defined scope and a handover at the end.

Engagements are scoped as statements of work.

Always patient and measured, with deep technical knowledge he was able to impart very effectively.

Matt CalthropFull-stack engineer · Via Experian

You might need this if…

  • A recommendation calls for a build and no team is free to take it on.
  • A prototype works but has never been hardened for production.
  • A manual, paper-based process costs more every year it stays that way.

Selected examples

  • OneShare Health. Designed and built an omni-channel enrollment pipeline from scratch across three channels, including the data model, the migration, and future-dated enrollments, so the service runs around the clock.

  • Experian. Built the design system as shipped code, not just design: coded components delivered to product engineers and maintained alongside the engineering teams that used them.

  • The 41st Parameter. Designed and built three separate product interfaces, owning the frontend architecture and code as well as the user experience.

  • Patterson Homes. Built a document processing pipeline for a largely paper-based home builder that dramatically simplified and accelerated management of subcontractors and home buyers.

  • e.Republic. Worked closely with the CIO to bring development in-house and build a publishing platform for the company’s writers, leading a team of six programmers.

NextHow we engage