About | Carmelo Bisignano

End-to-end product design

01
Understanding the context

I start where the product will live: the people who use it, what they are trying to get done and where it goes wrong today. Not every problem is worth solving, so part of the job is choosing the right ones.

Possible activitiesCompetitive analysis · User needs and behaviours · Field research · Interviews and observation · Problem definition
02
Shaping the concept

From what I learn, I sketch and prototype a few directions, test them early and keep the one that works. Workshops keep the business and the team in the loop, so the concept is shared before it is detailed.

Possible activitiesWorkshops · Design principles · Value proposition · Scenarios · Prototyping · Concept validation
03
Designing the details

Then the detail: flows, UI, copy, visual design and interactions, designed together so the product feels like one thing. Physical, digital or both.

Possible activitiesDesign language · Proof of concept · UX and UI design · Brand and visual design · Pattern library
04
Through the release

I stay with the engineering team while they build: planning, reviewing what ships, testing and fixing at every iteration, so the product that goes live is the one we designed.

Possible activitiesDesign system · Documentation · Pairing with developers · Design QA · Post-release improvements

Connected products & HMI design

01
System and context

Before any screen I look at the whole system: hardware, data flows, the people at the machine and the physical setting, from light and noise to gloves and safety rules. Business, design and engineering agree on the constraints up front.

Possible activitiesFeasibility studies · Hardware and software constraints · User and environment research · Device ecosystem map · Contextual inquiry on site · Usage scenarios
02
Interaction design

I define how people talk to the product: inputs and outputs, flows, states, alarms and feedback, sized for small screens, touch, buttons or voice. Every action gets a clear response.

Possible activitiesFlows and wireframes · State diagrams · Alarms and feedback · Touch, gesture and voice input · Sensor and input-output mapping · Accessibility
03
Prototyping on the device

I prototype on the real hardware or a close simulation, at the real resolutions and in the real conditions. Operators try it early, and we find the problems before they are expensive.

Possible activitiesHMI simulation · Prototypes across resolutions and devices · Hardware and software prototypes · Operator feedback sessions · Gesture and input tests
04
Handoff and integration

I turn the design into specs firmware and software engineers can build from, then check the result on the device, visual and behaviour. After launch, audits show what to adjust.

Possible activitiesDesign system for embedded UI · Engineering specs · Firmware and UI alignment · Usability QA in context · Integration testing · Post-release audits

AI product experience

01
Where AI helps

I start from the user’s problem and the business goal, and only then ask where AI really helps. Often it is one feature, not the whole product.

Possible activitiesUse case mapping · Value and risk assessment · Data availability review · Feasibility with engineering · Success metrics
02
Interaction and conversation

I design how people work with AI: prompts, suggestions, conversations, agents acting for them, and the moments when they take control back.

Possible activitiesConversational and agent flows · Prompt and input patterns · Human-in-the-loop interactions · Error, uncertainty and fallback states · Multimodal interactions
03
Trust

People need to see what the AI is doing, why, and how sure it is, and to check, correct or undo it. Privacy and the AI Act are part of the design, not an afterthought.

Possible activitiesExplainability patterns · Confidence and sources · Feedback and correction · Privacy and consent flows · AI Act and accessibility
04
Prototype and tune

I prototype with real models early, test with real outputs and tune behaviour, tone and guardrails with the engineers.

Possible activitiesCoded AI prototypes · Usability tests with real outputs · Evaluation criteria · Tone and guardrails · Iteration with ML engineers

Product discovery & strategy

01
Research

I find out what users need and where the current experience lets them down: journeys, real behaviour, the gaps between channels. Decisions later rest on this, not on opinions.

Possible activitiesCustomer journey mapping · Stakeholder workshops · Qualitative and quantitative research · Jobs to be done · Experience audits
02
Strategy

I connect what users need with what the business wants: which touchpoints matter most, where the opportunities are, and one vision the team can point to when priorities clash.

Possible activitiesTouchpoint priorities · Experience principles · Opportunity mapping · North Star vision · User segments
03
Planning the experience

The strategy becomes something teams can deliver: service blueprints, the interactions that matter, and who owns each part of the journey across channels and departments.

Possible activitiesService blueprints · Future-state journeys · Experience metrics · Friction priorities · Governance model
04
Putting it to work

Last, the habits that keep it alive: a roadmap, KPIs someone watches, rituals and feedback loops that hold the quality as the company changes.

Possible activitiesRoadmap · Team alignment · UX KPI tracking · Experience playbook · Feedback loops

Operational analytics & decision experience

01
Decisions first

I start from the decisions, not the data: who decides what, when, and with which information, from the operator on the floor to the manager planning the quarter. That shows where people lose time or guess.

Possible activitiesRoles and stakeholders · Decision inventory · Contextual inquiry with operators · Critical moments · Audit of current reports and tools
02
KPIs and data

With the business I pick the metrics that matter and fix how each is measured: sources, quality, thresholds. Every number on screen gets a meaning and an owner.

Possible activitiesKPI workshops · Metrics and thresholds · Data source and quality review · Information architecture · Alert and escalation rules
03
Dashboards and charts

I design how data turns into action: hierarchy, charts, alerts, drill-downs and a view for each role, live where it counts. Charts join the design system, and AI insights come with a way to check them.

Possible activitiesRole-based dashboards · Data visualisation guidelines · Real-time and alert states · Drill-down and filters · Explainable AI insights · Chart components
04
Testing and adoption

I test with the people who use the dashboards every day, in their real conditions, then watch how they are used and keep refining.

Possible activitiesTests with operators and managers · Decision tasks · Usage analytics · Iterations · Onboarding and docs

Prototyping & validation

01
Exploring ideas

Sketches, storyboards and quick demos get ideas out of heads and in front of people, so stakeholders agree on a direction early.

Possible activitiesIdeation sessions · Sketching and storyboards · Concept demos · Feasibility checks · Assumption mapping
02
Prototyping

I build prototypes at the fidelity the question needs: a clickable flow, a coded simulation, a device or a 3D scene. Often AI tools make the first version in hours.

Possible activitiesWireframes and clickable flows · High-fidelity prototypes · Coded prototypes · Device simulations · AR, VR and 3D prototypes · AI-assisted prototyping
03
Testing with users

I test with real users, moderated or remote, and combine what they say with what they do.

Possible activitiesModerated usability tests · Remote unmoderated tests · Interviews · Surveys and metrics · Task success · Accessibility tests
04
Learning and iterating

I turn the findings into a short list of changes, ship them and test again, until the evidence says it works.

Possible activitiesSynthesis of findings · Prioritised improvements · Iteration plan · Usability score tracking · Final validation

Design engineering

01
Design and tech choices

I check feasibility, accessibility and performance before the first screen, so what I design can be built the way it was meant.

Possible activitiesFeasibility assessments · Technology choices · Accessibility (WCAG, EAA) and performance checks · Dev tooling setup
02
Designing in code

I design modular from the start: recurring patterns become components and tokens. Working prototypes in code, often built with AI tools, show how a solution behaves and where it breaks.

Possible activitiesModules and core features · Content hierarchy · Coded prototypes and proofs of concept · AI-assisted prototyping · Lean experiments · Token sync with React and Vue
03
Code and handoff

I write and review front-end code with the developers, with care for accessibility, performance and developer experience. States and flows are specified, so nothing gets lost on the way to production.

Possible activitiesFront-end development · HTML and CSS pairing · Component and state docs · Handoff walkthroughs · Accessibility layer · Design-to-code guidelines
04
QA and scale

Design QA and visual regression tests keep the UI true to the design on every platform. After launch I tune the architecture, performance and theming for more brands and languages.

Possible activitiesDesign QA scripts · Visual regression tests · Cross-browser and responsive checks · UI bug triage · Performance and accessibility audits · Theming and multi-brand

Design systems

01
Audit and foundations

I start from what exists: components, styles, code and how teams really use them. Then I set the foundations: tokens, type, colour, spacing and accessibility rules.

Possible activitiesUI inventory and audit · Token architecture · Accessibility foundations (WCAG, EAA) · Naming conventions · Tool and process audit
02
Components and patterns

I design the components the products really need, with every state and variant, in Figma and in code at the same time.

Possible activitiesFigma component library · Coded components (React, Vue, Storybook) · States and variants · Pattern docs · Chart components
03
Governance

A design system lives only if teams use it and add to it. I set how changes are proposed, reviewed and released, versioned in git and documented.

Possible activitiesContribution model · Versioning and release notes in git · Documentation site · Design and dev reviews · Adoption tracking
04
Scale and automation

I extend the system to new brands, platforms and languages, and automate the chores: token sync, docs, checks between Figma and code.

Possible activitiesTheming and multi-brand · Token sync pipelines · Automated design QA · Figma-to-code checks · Version control for design files · Team training

AI & automation workflows

01
How work flows today

I map how design and product work really moves: requests, handoffs, reviews, releases. The repetitive steps, the waiting and the copy-pasting show up fast.

Possible activitiesWorkflow mapping · DesignOps alignment · Tool and process audit · Bottlenecks · Automation backlog
02
Designing the automation

I design the flows and the points where people stay in charge: what runs alone, what needs a review, what happens when something fails.

Possible activitiesn8n workflows · API integrations · Human-in-the-loop checkpoints · Errors and fallbacks · GDPR and data sovereignty
03
AI agents and tools

I set up AI agents and tools inside the team’s work: research synthesis, content, design QA, docs, design-to-code. Each has one job and a way to check its output.

Possible activitiesAI agent setup · Prompt and context design · Design-to-code pipelines · Automated docs · AI-assisted design QA · Git-based design workflows
04
Adoption

I roll the workflows out with the team, measure the time they save and refine them. The team owns them, documented, so they keep running after I leave.

Possible activitiesOnboarding and training · Time and quality tracking · Workflow docs · Retrospectives · Maintenance

Visual design, motion & 3D

01
Visual direction

I set how the product looks: type, colour, layout, imagery and the tone they give the brand. I explore it on real screens, not in a moodboard alone.

Possible activitiesStyle exploration · Visual language and UI style · Typography and colour · Icons and illustration · Brand to product
02
Motion

I design how things move: transitions, feedback, scroll stories and micro-interactions that explain the interface, not only decorate it. Every duration and curve is specified.

Possible activitiesMotion principles and tokens · Micro-interactions · Page and state transitions · Scroll-driven stories · Reduced-motion versions
03
3D and WebGL

When a moment needs more, I model in Blender and bring it to the browser: 3D scenes, shaders, particles and generative graphics, light enough for an everyday laptop or phone.

Possible activities3D modelling in Blender · Materials, lighting and renders · glTF export for the web · Three.js and WebGL scenes · Custom shaders · Generative visuals
04
Built in code

I ship motion as code, not as a video to copy: GSAP and CSS that developers can lift into the product, tested on real devices.

Possible activitiesGSAP and CSS animation · Interactive prototypes in code · Lottie and video exports · Motion specs for developers · Performance budgets · QA on real devices

I came from architectural drafting and illustration, through graphic and web design, to SaaS as companies went digital.

What I can do for your product, your business and your team.What I can do for your product, your business and your team.

Understanding the context

Shaping the concept

Designing the details

Through the release

System and context

Interaction design

Prototyping on the device

Handoff and integration

Where AI helps

Interaction and conversation

Trust

Prototype and tune

Research

Strategy

Planning the experience

Putting it to work

Decisions first

KPIs and data

Dashboards and charts

Testing and adoption

Exploring ideas

Prototyping

Testing with users

Learning and iterating

Design and tech choices

Designing in code

Code and handoff

QA and scale

Audit and foundations

Components and patterns

Governance

Scale and automation

How work flows today

Designing the automation

AI agents and tools

Adoption

Visual direction

Motion

3D and WebGL

Built in code

What people say

What I can do for your product, your business and your team.