Daniel Motza
Daniel Motza

{{ t.hero_kicker }}

{{ w.t }}

{{ t.hero_sub }}

7+ yrs · 50+ products · 2M+ users
{{ m.v }}
{{ m.l }}

Companies I’ve worked with

IEC
IAI
IntsightsNoogata
BIGI
EL ALBulwarx
SysAid
Rapid7ASK-Y
Clalit
AbraCal
Gov.il

{{ t.wk_heading }}

{{ t.wk_note }}
Private → In orbit soon

{{ w.title }}

{{ w.year }}
{{ w.tag }}

{{ w.desc }}

{{ w.cta }} →

{{ t.ab_heading }}

{{ t.ab_sub }}

{{ a.num }}

{{ a.title }}

{{ a.title }}

{{ a.desc }}

{{ a.tools }}

{{ t.pr_heading }}

{{ t.pr_sub }}

Stage 01 / 05 Discovery
01 · Discovery
02 · Strategy
03 · Design
04 · Validate
05 · Ship
01/ 05
Stage

Discovery & Research

Interviews, data, and market context to frame what is genuinely worth building - before a single pixel moves.

Deliverables
User interviews Data & analytics Market context
02/ 05
Stage

Strategy & Definition

Ambiguity into sharp strategy: clear success metrics, priorities, and a plan everyone can commit to.

Deliverables
Success metrics Priorities Roadmap
03/ 05
Stage

Design & Systems

Flows, interfaces, and scalable systems built for consistency and speed - craft that survives production.

Deliverables
Flows UI design Design system
04/ 05
Stage

Prototype & Validate

AI-accelerated prototypes tested with real users - we learn before we build, not after.

Deliverables
Hi-fi prototypes User testing Fast iterations
05/ 05
Stage

Ship & Iterate

Close partnership with engineering to reach production, then measure impact and refine.

Deliverables
Dev handoff QA & polish Measure & refine
01/ 05

Discovery & Research

Interviews, data, and market context to frame what is genuinely worth building - before a single pixel moves.

Deliverables
User interviews Data & analytics Market context
02/ 05

Strategy & Definition

Ambiguity into sharp strategy: clear success metrics, priorities, and a plan everyone can commit to.

Deliverables
Success metrics Priorities Roadmap
03/ 05

Design & Systems

Flows, interfaces, and scalable systems built for consistency and speed - craft that survives production.

Deliverables
Flows UI design Design system
04/ 05

Prototype & Validate

AI-accelerated prototypes tested with real users - we learn before we build, not after.

Deliverables
Hi-fi prototypes User testing Fast iterations
05/ 05

Ship & Iterate

Close partnership with engineering to reach production, then measure impact and refine.

Deliverables
Dev handoff QA & polish Measure & refine

{{ t.rc_heading }}

{{ r.name }}
{{ r.role }}
{{ r.tag }}
{{ r.quote }}
Daniel in space
Hover to enter orbit move your cursor across the photo

{{ t.ab2_heading }}

{{ t.ab2_p1 }}

{{ t.ab2_p2 }}

{{ t.ab2_p3 }}

{{ s.text }}
Beyond the pixels
{{ lp.t }}
{{ lp.d }}
The AI-native flight deck
💻 FigmaFigma ClaudeClaude ChatGPTChatGPT MobbinMobbin MixpanelMixpanel MiroMiro JiraJira MazeMaze AdobeAdobe

{{ t.ct_heading }}

{{ t.ct_sub }}

{{ ctErrMsg }}
Response within 24h
Transmission received

Your message is on its way to mission control - I'll get back to you within 24 hours.
{{ t.ct_l_email }}
danielmotza@gmail.com
{{ t.ct_l_phone }}
050-900-3999
{{ t.ct_l_loc }}
{{ t.ct_v_loc }}
LinkedIn
Daniel Motza
Daniel Motza - {{ t.footer_tag }}
© {{ year }} · {{ t.ct_v_loc }}
Mission log
Mission accomplished
Thanks for making the journey - now let's launch yours.
Daniel Motza
Missions
{{ cn.label }}

{{ activeCase.tag }}

{{ activeCase.title }}

{{ activeCase.summary }}

{{ coverEl }}
{{ t.cd_l_role }}
{{ activeCase.role }}
{{ t.cd_l_timeline }}
{{ activeCase.timeline }}
{{ t.cd_l_team }}
{{ activeCase.team }}
{{ t.cd_l_platform }}
{{ activeCase.platform }}
{{ t.cd_l_overview }}

{{ activeCase.overview }}

{{ activeCase.challengeTitle }}

{{ activeCase.challenge }}
{{ t.cd_l_approach }}

{{ ap.t }}

{{ ap.d }}
Research & discovery

{{ activeCase.researchNote }}

{{ r.v }}
{{ r.l }}

{{ rp.t }}

{{ rp.d }}
Who we designed for
{{ pe.t }}

{{ pe.d }}
The principles it led us to
{{ pr2.t }}

{{ pr2.d }}
Wireframes & prototypes

{{ activeCase.wireNote }}

Prioritization

The impact / effort map

I mapped every candidate feature with the team on an impact / effort matrix, then sequenced delivery: ship the quick wins first for fast value while the big bets were designed in parallel.

Impact →
{{ qd.q }} {{ qd.hint }}
{{ it }}
Effort →
The queue, reframed

From four problems to four moves

The research pointed at four clear problems with the legacy queue. I designed a deliberate answer to each.

Problem
{{ ps.p }}

{{ ps.pd }}

My move
{{ ps.s }}

{{ ps.sd }}
The redesign

The main ticket table

The heart of SysAid. I rebuilt it around scanability and speed - clearer hierarchy, status and priority cues, bulk actions and multi-select - so agents move through queues with far less friction.

BEFORE
Main ticket table before
AFTER
Main ticket table after
What makes the queue fast
{{ qf.t }}

{{ qf.d }}

Ticket page & insight panel

I rebuilt the single ticket into a focused two-column view with a contextual insight panel (open SRs, relevant KB, time-to-repair) and a clear activity journey - plus complex reusable components like the multi-select assignee.

BEFORE
SysAid ticket page before
AFTER
SysAid ticket page after
The right-side tabs I designed
{{ tt.t }}

{{ tt.d }}
Flagship feature

Template Designer - a no-code builder

A huge feature I owned end-to-end: a low-code / no-code builder that lets non-technical people compose ticket templates for their organization - sections, fields, workflows, and per-field properties - by dragging from a field library, with a live preview. It put template creation in the hands of the teams who actually run the processes.

SysAid Template Designer
Foundation

The design system

I created and maintained the design system from scratch - color, typography, an icon set, and complex components with every state documented - so the whole platform stays consistent and ships faster.

SysAid design system
End to end

Across the product lifecycle

I stayed close to the product from first research to post-launch measurement - not just the design phase. Each stage fed the next.

{{ ls.n }}
{{ ls.t }}

{{ ls.d }}
How I measured success

Before → after

{{ activeCase.metricsNote }}

{{ mt.metric }}
{{ mt.before }} {{ mt.after }}

{{ mt.d }}
Research & discovery

Classified means no interviews, no analytics, no recordings. So research became a discipline of proximity: recurring on-site sessions at the client's offices, where the operations manager walked me through how the current system is really used - the commands operators fire most, the failures they chase daily, and how critical uptime is to the whole operation. Every design decision traced back to that picture.

On-site working sessions

Recurring physical meetings at the client's offices - the only research channel a classified program allows.

Proxy feedback loop

The operations manager was the voice of the operators - usage patterns, requirements, and feedback on every iteration.

Frequent-actions inventory

A mapped inventory of the commands, checks and calibrations operators run daily - ranked by frequency and criticality.

Legacy system audit

A deep walkthrough of the existing system and the pain it causes every day - the baseline the new design had to beat.

Where they started

The system they had

This is the interface operators actually worked in before we arrived - a dense grid of near-identical panels, colour-coded state, and repeated controls with no hierarchy or search. Everything competed for attention at once. It set the bar the new system had to beat, and it is the reason a flexible, no-code, search-first console mattered so much.

The legacy system In daily use for years before the redesign - blurred for classification. Dozens of identical panels, colour-coded state, repeated controls, no hierarchy and no search.
Prioritization

The impact / effort map

With no analytics to lean on, prioritization came straight from the ranked frequent-actions inventory. I mapped every candidate on impact / effort and shipped the quick wins first while the big bets were designed in parallel.

Impact →
{{ qd.q }} {{ qd.hint }}
{{ it }}
Effort →
Concept Design Review

Two concepts, one validated direction

Before committing to build, I ran a CDR - a Concept Design Review with the client and development - to validate a direction both operationally and technically. I brought two concepts to the table.

Selected Concept A

Tabbed workspace

A browser-like model - think Chrome tabs - where every tab is a full screen of operational elements. Operators jump between the areas they need to run, pull real-time data, and act in the least time and fewest clicks possible. Fast, familiar, and built for real-time operation.

Explored Concept B

Aircraft hologram

A 3D hologram of the aircraft as the navigation surface - operators would reach screens by moving through the model. It looked striking, but it never gave real comfort for real-time operation: more gimmick than tool, so I set it aside.

The client and development loved the tabbed workspace, and it earned the technical and practical validation to move forward - it became the operator console that follows.

The solution

The operator console

Live telemetry streams into configurable sections - sensors, meters, cameras, toggles and commands - while a status panel surfaces connection state and activity failures the moment they happen. Operators see, decide and act on a single screen, at speed.

IAI real-time monitoring console

Automated macros for maintenance & calibration

Routine check and calibration flows run as macros - step-by-step sequences with live progress, remaining time, and a drill-down into every failure with its recommended action. Work that used to demand deep technical knowledge became a guided flow operators move through quickly.

IAI macro runner with failure drill-down

Browser-fast navigation

Screens live in tabs, and every new tab opens on search plus the most common pages with their quick actions attached - so reaching any screen or firing a frequent command takes seconds, not menus.

IAI new tab - search and common pages
Flagship feature

UI Builder - operator screens without code

The interface is fully flexible: an admin composes the screens his operators work on by dragging elements straight from the ICD onto sections, tuning each element's properties in place, and publishing. Low-code and no-code by design - building a screen requires no technical sense, so the interface adapts to the operation instead of the other way around.

IAI UI Builder - composing a screen IAI UI Builder - element properties
Craft & methodology

The system behind the system

{{ activeCase.dsIntro }}

{{ df.t }}

{{ df.d }}
{{ g.t }} {{ g.c }}

Real frames from the IAI design-system and Element Index files in Figma - the reference developers implemented against.

Decision log

Trade-offs I made

Real programs are full of tension between the ideal design, engineering reality, and how people actually work. A few calls I owned:

{{ dc.tag }} {{ dc.title }}
The idea

{{ dc.idea }}

The tension

{{ dc.tension }}

The call

{{ dc.call }}
End to end

Across the product lifecycle

In a classified program I owned the whole arc - from on-site discovery to a production system and the feedback loop that kept improving it.

{{ ls.n }}
{{ ls.t }}

{{ ls.d }}
How I measured success

Before → after

{{ activeCase.metricsNote }}

{{ mt.metric }}
{{ mt.before }} {{ mt.after }}

{{ mt.d }}
Challenges

Three problems, three moves

Challenge
{{ ps.p }}

{{ ps.pd }}

Solution
{{ ps.s }}

{{ ps.sd }}
Prioritization

The impact / effort map

With a broad public audience and a real accessibility duty, I mapped every decision on impact / effort - shipping the quick wins that helped people find and book fast, while the big bets like accessibility and responsiveness ran in parallel.

Impact →
{{ qd.q }} {{ qd.hint }}
{{ it }}
Effort →
The experience

From discovery to done

{{ activeCase.flowIntro }}

{{ g.t }} {{ g.c }}
Craft & consistency

A style guide to keep it whole

{{ activeCase.styleNote }}

{{ activeCase.styleCap }}
Responsive

Built for every screen

{{ activeCase.mobileIntro }}

{{ mb.t }}
End to end

Across the product lifecycle

As the sole lead designer I carried the portal end to end - from the brief with the PM and Clalit studio to an accessible, responsive product and a style guide that keeps it whole.

{{ ls.n }}
{{ ls.t }}

{{ ls.d }}
How I measured success

Before → after

{{ activeCase.metricsNote }}

{{ mt.metric }}
{{ mt.before }} {{ mt.after }}

{{ mt.d }}
Overview

One designer, product to brand

{{ activeCase.ovIntro }}

Product
  • {{ op.t }}
    •
Brand
  • {{ ob.t }}
    •
Prefer to watch? The Clara film, 2:57.
Jump to the Film chapter.

Part 1 · Product

Research

Operators needed control, not chat

{{ activeCase.researchNote }}

{{ r.t }}

{{ r.d }}
Pipeline

One pipeline, not four projects

{{ activeCase.pipelineIntro }}

{{ pl.n }}
{{ pl.t }}

{{ pl.d }}
Design system

A system you change in one place

{{ activeCase.dsIntro }}

{{ ds.v }}
{{ ds.l }}
{{ th.t }}
{{ activeCase.dsThemeCap }}
Five colour modes · 0:17 · No soundRecorded in the clickable prototype. One set of components serves every mode, so no screen is designed twice.
What you see

The same dashboard in Dark Graphite, Dark Emerald and Dark. The theme toggle switches to Light Snow, then Light, and back to Dark and Dark Graphite. Layout and components stay the same; only colour changes.

Handoff

Every feature is a script

{{ activeCase.handoffIntro }}

{{ cv.c }}
Flagship

Sixteen features, four that carry it

{{ activeCase.flagshipNote }}

{{ fs.t }} {{ fs.c }}

Watch two of them run

Workflow editor · 0:24 · No soundRecorded in the clickable prototype. Problems show up where they are fixed, not after an agent goes live.
What you see

An Execution step is added to a workflow. Validate flags 3 problems and the inspector lists them. An agent, an instruction and a tool are chosen, and Validate passes: 7 steps. Run Test then shows each step with its timing, all ticks green.

RAG Config Builder · 0:25 · No soundRecorded in the clickable prototype. Each setting arrives with its reason, so teams can check it before trusting it.
What you see

An agent is described in plain language and a sample file of 1,284 records is uploaded. Generate streams a configuration. The result is marked valid, with an Explanation of the search backend, weighted fields, filters and scoring. Sample output, prepared for the prototype.

Decisions

What I chose, and what I left

{{ activeCase.decisionsIntro }}

{{ dc.tag }}

{{ dc.title }}

{{ dc.d }}

Part 2 · Brand

Identity

One lockup, one accent, a calm voice

{{ activeCase.identityIntro }}

Navy on cream
Navy on white
White on navy
White on a dark image
  1. 1Navy lockup on cream and white.
  2. 2White lockup on navy and dark images.
  3. 3No third version: no amber, grey, gradient or outline.
Two versions onlyThe ground picks the version, so no one decides it case by case.
  • Cream#f4f1e9 · about 60%Ground · brand-cream
  • Navy#0a0f2e · about 25%Ink and headlines · brand-navy
  • Warm grey#55504a · about 10%Body text · text-body
  • Amber#fe9f03 · 5% or lessAccent · brand-amber

White (brand-white #ffffff): cards only.

Proportion, not paletteAmber stays at 5% or less so it can point without shouting.

Agents that do the work, under your rules.

Switzer 400 · headlines

Plain, specific and calm. The senior architect who's done it.

Inter 400 / 500 / 700 · reading

Type rolesOne family to speak, one to read, so every page sounds the same.
Road not taken · Oct 20After 20+ directions, I took a house-of-agents logo as far as a film; my manager did not approve it, so the live lockup stayed.
Brand system

A design system for people and AI tools

{{ activeCase.brandSysIntro }}

Components
35
Colour tokens
39 x 2 themes
Imagery families
7
DS
v1.6.1
Light Silk · default ground
Navy Silk · the one dark moment
Silk family · since v1.6.0Born on the portal, Silk replaced the old Light waves backgrounds for new work.
Colour pairs with contrast ratios
PairRatioLevel
Ink on creambrand-navy on brand-cream16.6:1AAA
Text body on creamtext-body on brand-cream7.1:1AAA
Accent text on creamaccent-text on brand-cream5.3:1AA
Amber on navybrand-amber on brand-navy9.1:1AAA
White on navybrand-white on brand-navy18.7:1AAA
Text muted on creamtext-muted on brand-cream3.3:1Large only
Amber on creambrand-amber on brand-cream1.8:1Never text
Rated pairsWhen words need the accent, darker accent-text stands in and passes AA.
Brand book · Extended p76Showing the wrong version next to the right one stops a rule being misread.
Silkopeners
Navy platescharts and data
Glassproduct
Clayarchitecture
Sectorsindustries
AI agent
Portraitsagents
Film stillsvideo

Navy Silk opens and closes; navy plates hold charts. The amber line is never cropped out.

Seven familiesAll made in-house, no stock and no baked text, so every image stays ours.
Website

A website an executive gets in 30 seconds

{{ activeCase.siteIntro }}

See it live: scully-ai.com (opens in a new tab)

{{ sl.t }}
{{ sl.c }}
{{ sp.t }}
{{ sp.c }}
{{ sm.t }}
{{ sm.c }}
Film

A film led by one agent

{{ activeCase.filmIntro }}

2:57 15 MB Has sound
What happens in the film

{{ activeCase.filmStory }}

{{ fk.t }}
{{ fk.c }}
Book and portal

A book for the rules, a portal for everyone else

{{ activeCase.bookIntro }}

  • Extended edition

    113

    pages · rules and wording

  • 26

    pages · slim edition, for teams and agencies

  • Recipe kit

    106

    pages · the prompts behind the imagery

Three editionsOne book, cut per reader, so nobody reads 113 pages to make a slide.

Recipe kit · 1a Sculpted ribbon plate · part 1 of 2

  • Fixed: keep word for word
  • {Slot}: change within the range

Pure abstract texture photograph, no typography whatsoever. Soft sculpted matte ribbons of warm cream and pale ivory with faint cool pale-blue shadows, gentle diffused studio light from the upper left, subtle fine grain. {FORM: Parallel ribbons flow horizontally edge to edge; near the centre, slightly above the middle, they gently crowd together and rise into one smooth calm audio-waveform swell, tallest at the centre, tapering to flat quiet ribbons at both sides.} A single very thin warm amber highlight line runs along the top of the crest of the tallest ribbon only, not in a groove.

Slot range: 3 approved forms (horizontal swell, concentric arcs, diagonal pulse).

Recipe kit · promptWritten for whoever generates next, so the look survives without me in the room.
Brand portal · privateBuilt in the website's look, so the portal itself teaches the brand.
01StoryScully does real work and says it plainly.
02VoicePlain words, real outcomes, a source for every number.
03LogoThe lockup is our signature, so we never edit it.
04ColourCalm is a colour choice: mostly cream, amber only to point.
05TypeQuiet type sounds confident: Switzer to headline, Inter to read.
06ImageryOne family per frame keeps every image calm and ours.
07Use itMost work needs no approval; the rules exist so you can ship.
08FilesCopies of copies are where a brand breaks first.
Eight sectionsEach section opens with one line of why, before any rule.
  • Brand book, slim editionThe 26 boards behind this page.PDF · 6.6 MB
  • Lockup, navyFor cream and white grounds.SVG · 12.3 KB
  • Lockup, whiteFor navy and dark images.SVG · 12.2 KB
  • Small SFavicons and app icons, 32px or smaller.SVG · 0.7 KB
  • Silk backgrounds · 1920For slides, social and web.ZIP · 8 JPG · 2.0 MB
  • Silk print mastersFor print and large screens.ZIP · 8 JPG · 21.5 MB
FilesSame names as the design system, so nobody works from a copy.

Portal message when reduced motion is on: Motion is reduced to match your device setting.

The portal's Pause button for the moving hero, reading: Motion off

prefers-reduced-motion: reduce

Reduced motionMotion is optional: a Pause control, plus a full version for reduced-motion settings.

Three sources, one version line

  1. Brand book (Figma)Rules and wording
  2. From Brand book to Portal: wording: the book wins
  3. PortalSlim edition and downloads
  4. From Design system to Portal: files: same names
  5. Design systemValues and files
  6. From Portal back to Brand book: sync-check.py: portal text vs book

Every plan that touches one ends with a sync step.

Brand syncOne home per fact, so there is only one place to be right.
  • Brand book v2.2 · DS v1.6.1 · Nov 2026book footer, 108 of 113 Extended and 24 of 26 Slim pages
  • Brand book v2.2 · DS v1.6.1 · Brand owner: Daniel Motzaportal, 8 section footers
  • version: 1.6.1DESIGN.md front matter, which names book v2.2

On all three: Brand book v2.2 · DS v1.6.1

One version lineAnyone holding a page can tell at a glance if it is current.
Outcomes

Product and brand, shipped and in step

{{ activeCase.outcomesIntro }}

{{ so.v }}
{{ so.l }}
{{ t.cd_l_outcomes }}
{{ o.v }}
{{ o.l }}
{{ t.cd_next }}
{{ nextCase.title }}
→
{{ activeRec.name }}
{{ activeRec.role }}
{{ activeRec.tag }}
{{ activeRec.quote }}
{{ recCounter }}
Classified mission

Restricted airspace

The {{ pinCaseTitle }} mission is classified. Enter the 4-digit launch code to open the full case study.

Access denied - that code doesn't match mission control's records. Access granted - opening mission

Don't have the code? Request clearance
Daniel Motza
Signal lost

Error 404 · Signal lost

Lost in deep space.

These coordinates don't map to any page in this galaxy. It may have drifted out of orbit - or never existed at all.

Report a lost page
404 · Page not found · Design not of this world
Daniel Motza
Systems malfunction
!

Error 500 · Systems malfunction

Houston, we have a problem.

Something failed on our side of the transmission. Mission control has been alerted and is already on it - try again in a moment.

500 · Internal error · Design not of this world
{{ lbCount }}
{{ lbLabel }} {{ lbCap }}
Playground
{{ pi.cap }}
Playground
Off-duty orbit
Side quests, experiments and small joys floating between missions.
Drag to explore · click an item to zoom