Graph Database Workflow — Hand-Drawn Explainer Video for Elephant Bird Consulting

The Visual Problem

How do you draw a software workflow?

For Elephant Bird Consulting, I created an illustrated explainer video showing how a graph database project moves from an initial client requirement through architecture and database administration to developer implementation.

The subject could easily have become a screen full of diagrams, nodes, arrows and software terminology. Instead, the film gives the process a human structure. Each technical role becomes a character, each handover becomes an action, and the underlying code and data logic are reduced to simple coloured forms that can be physically manipulated inside the story.

The aim was not to remove the technical logic. It was to give that logic a visual form that could be followed by both specialist and non-specialist viewers.

01 · Character Design

Original people for each stage of the workflow

The visual structure follows four recognisable roles: client, software architect, database administrator and development team. Each was designed as an individual character rather than represented by an icon or anonymous silhouette.

That matters because this is ultimately a story about collaboration. Requirements are interpreted, structures are developed, information is handed over and implementation follows. Showing people making those decisions gives the viewer a much clearer route through the process.

02 · Visual Abstraction

Boiling code down into primary-coloured blocks

One of the central visual decisions was to give complex software structures a deliberately simple physical vocabulary. Code, relationships and data architecture become blocks, cubes and connected geometric objects built from a restrained primary-colour system.

That reduction allows the audience to concentrate on the logic of the process rather than on the appearance of a specific interface. A technical structure can be assembled like a puzzle, examined by the architect, handed to the database administrator and eventually passed into development.

The blocks do not pretend to be the software itself. They are a visual language for relationships, structure and handover.

03 · Drawing Process

Timelapse drawing as part of the explanation

The whiteboard treatment uses the drawing process itself as part of the visual pacing. Characters, objects and data structures appear progressively rather than arriving as completed illustrations all at once.

That timelapse progression is useful for technical communication because it controls the order in which information enters the frame. The viewer watches the idea being built at approximately the same time as the explanation develops.

04 · Workflow Storytelling

A technical process becomes a sequence of handovers

A useful workflow animation needs more than a set of attractive frames. The viewer has to understand what changes between them.

Here the structure is deliberately simple: the client defines a need; the architect gives it structure; the database administrator prepares and manages the environment; and the development team receives what it needs to implement the solution. Each transition is shown as an action rather than explained only in words.

Technical Communication

Making specialist subjects readable without making them simplistic

Technical subjects often contain several levels of information at once: specialist terminology, roles, systems, sequence and dependencies. Trying to show all of them literally can make an explanation harder rather than easier.

The useful visual decision is often to determine what the audience actually needs to understand at each moment. In this project, character design explains responsibility, coloured objects explain structure, handovers explain workflow and animation explains sequence.

Project Details

Elephant Bird Consulting