Work Archive About Advisory Email me
Open to VP / Director / Head of UX

Driving outcomes with precision

A design leader who stays close to the work. I still do the product thinking. Most recently at iCapital, I led design while platform assets and company headcount roughly tripled.

See the work Résumé
Greg Dilley

How I work

The system behind turning reactive design into a strategic function.

Make research operational

I build the discovery and measurement practices that give a design team a number to manage by.

Build and structure teams

I turn reactive, downstream studios into specialized teams with a seat where the decisions get made.

Turn strategy into shipped product

I frame the problem at the whiteboard and stay close to the work until it ships.

You are a very good leader. I would hire you again in a heartbeat, anywhere I went.
CIO, Fintech

{{ cs.groupLabel }}

{{ cs.imageAlt }}
{{ hl.num }} {{ hl.name }}
{{ cs.kicker }}

{{ cs.title }}

{{ cs.oneLiner }}

Read the case study →
“
The results of this work are not splashy, but the foundations of our solutions are stronger because of the processes instilled by Greg.
UX Designer, from a farewell note to the CEO
Greg has become the most important mentor I have ever had, from bandaid production work to identifying root problems.
UX Designer, direct report

In the UX community

NYCUXPA

Facilitator

Scaled a single-evening Design Studio sprint for 90+ enterprise practitioners across 9 cross-functional units, blank page to concept presentation in one night.

NYCUXPA design studio
NYCUXPA design studio
Greg Dilley, informal

Beyond the work

Soccer, lifelong. Playing since I was a kid, into college. A team is only as strong as its movement off the ball, the same lesson I apply building design organizations.

Married my college love. Three kids later, we get to watch them play the same game, and still sneak out on a date.

Outside of work I'm building or fixing something around our NJ home: a pizza oven, a garden, whatever needs it. Same process as the day job: find the constraint, build the system, stay in the trenches.

Where it started

A decade of hands-on craft, 2007 to 2016, before I led teams. Selects, not current work.

{{ item.caption }}

“A star performer on any team.” Experience Design Leader, TD Ameritrade

{{ activeArchiveItem.caption }}
{{ activeArchiveItem.caption }}

Advisory & Consulting

I'm currently accepting a limited number of advisory engagements through White Matter UX, while exploring full-time VP / Director / Head of UX roles.

Fractional Advisory

Partnering with founders part-time to anchor product roadmaps and design systems in research, not founder hunches.

Design Execution

Deep information architecture and rapid, AI-accelerated execution, so teams build the right thing, test it, and ship it fast.

Talent Placement

Practitioner-led vetting, using two decades in UX to deliver elite, research-backed design talent.

Learn more about White Matter UX →      

Let's drive the outcomes your product deserves.

Email me LinkedIn Résumé
© {{ year }} Greg Dilley, greg.dilley@gmail.com
{{ activeImageAlt }}
{{ activeCs.kicker }}

{{ activeCs.title }}

{{ activeCs.confidentialNote }}

The challenge

{{ activeCs.challenge }}

Representative work

{{ hl.name }} {{ hl.line }}

The approach

{{ para }}

Representative work

{{ hl.name }} {{ hl.line }}

The context

{{ st.value }} {{ st.label }}

Company growth, Oct 2021 to May 2026, from iCapital public announcements.

The impact

  • {{ line }}

Source: {{ activeCs.impactSource.label }}

{{ activeCs.relatedNote }}

{{ screen.caption }}
{{ screen.caption }}
Service Genie running live: a real demo, not a mockup Watch on YouTube
{{ shot.caption }}
{{ shot.caption }} Source: {{ shot.source }}

{{ activeCs.creditLink.label }}: chukwudi.co/project/realogy-design-system

Watch: staff training video

At an alternative investments platform, every new fund meant hiring more people to do operations work by hand. I led design and the program to change that, one process at a time: AI does the collecting, people do the checking.

PartnerCOO
My roleHead of UX and program lead
Scope4 processes, 3 projects, 1 year

The problem

Every new fund meant hiring more people to do the work by hand.

  • Who: operations teams running fund processes such as capital statements, letters of authorization and fund launches.
  • What was broken: the work happened between disconnected tools. People compared data, copied values and approved by hand. They were collectors.
  • Why it mattered: operations was one of the largest parts of the company, and its cost grew with every new fund. Manual work also added operational risk.
Before and after: collecting versus checking Left: one ops person jumps between nine separate systems in a tangled path. Right: a workflow engine gathers from the same systems and the person checks everything from one task board. BEFORE Collecting 1 2 3 4 5 6 7 8 Compare data Copy values Approve by hand The work happened between the tools AFTER Checking Engine AI gathers and routes the work One task board AI collects; the person checks and approves
Collectors jump between systems. Checkers work one queue.Illustrative

My role

Head of UX and program lead for a company-wide automation program.

  • Partner. I partnered with the COO. The AI team built the automation.
  • Program and design. I ran the program as well as UX: tracked every piece of the work, cleared blockers and drove the design. I reported progress to senior leadership every two weeks.
  • Player/coach. I was at the whiteboard with my team on the solutions.
  • The design goal. I set it: make ops people checkers of information, not collectors of it.

Approach

The workflow engine as the backbone, the landing page as the surface.

  • Map the work first. The ambiguity was where to start among dozens of tools. We sat with ops staff to map their work, then ranked processes with the COO's team.
  • Design the system before the screens. A workflow engine routes data, tasks and hand-offs between people and tools. Ops users work from one landing page; leadership tracks progress in one management view.
  • Build in slices. Start with one process and the simplest useful surface, prove it with ops users, then extend module by module.
System design Three layers. Six existing tools at the bottom feed a workflow engine in the middle, which routes data, tasks and hand-offs. The engine feeds two surfaces at the top: the ops landing page, where ops users work, and the management view, where leadership tracks progress. EXPERIENCE ORCHESTRATION EXISTING TOOLS Ops landing page Where ops users work Management view Where leadership tracks progress Engine Routes data, tasks and hand-offs between people and tools Fund datasystemDocumentrepositoryReconciliationtoolCapital eventstoolSpreadsheetsEmail
Design the system before the screens: the engine mattered more than any single page.Illustrative

The 4 workflows

Four processes, combined into three projects.

I was given one year to deliver four processes. Two were similar enough to share a solution, so I combined them into one project. That bought time for the rest.

01

Capital statements

Combined with NAV into one project. Went first, to prove the pattern.

02

NAV

Close enough to capital statements to share one solution.

03

Letters of authorization

A high-volume process with a clear checking step.

04

Fund launch

A broader process with more hand-offs between teams.

How we prioritized

Ranked by effort, time saved and risk.

With the COO's team, I ranked processes on how much manual work each carried against how risky or hard it would be to change. We started where the pattern could be proven fastest.

Prioritization chart A two by two chart with volume or time saved on the horizontal axis and risk or effort on the vertical axis. Four unlabeled dots mark the four processes; two sit close together inside a dashed ring, showing they were combined. The high volume, low risk quadrant is marked start here. VOLUME / TIME SAVED → RISK / EFFORT → START HERE
Four processes, two close enough to combine.Illustrative

Program timeline

Program timeline Four phases in sequence: discovery with ops, workflow mapping, pilots, and rollout. 01 Discovery with ops Sat with ops staff to map their work 02 Workflow mapping Ranked processes by effort, time, risk 03 Pilots First slice designed and tested with ops 04 Rollout One process at a time, one module at a time
Each process moved through the same four phases.Illustrative

Outcomes

Signed off, tested and called “life changing.”

  • “Life changing”: how the ops leader who would benefit most described the first project.
  • Signed off by the COO and the head of Product.
  • Tested: the first project was designed and tested with ops users.

What I learned

Design the system before the screens

The workflow engine mattered more than any single page.

Ship one process completely

Finish one before starting the next, and let it prove the pattern.

Look for shared solutions

Combining two similar processes into one project bought time for the rest.