Case Studies

Case-studies from SAP Signavio

01

Suite Approval Foundations

01

Suite Approval Foundations

01

Suite Approval Foundations

02

Change Propagation

02

Change Propagation

02

Change Propagation

03

Design System

03

Design System

03

Design System

04

Read-Confirmation

04

Read-Confirmation

04

Read-Confirmation

05

Governance App Modernisation

05

Governance App Modernisation

05

Governance App Modernisation

01 /

Highlights

SAP

Out-of-context highlights from my time at SAP

Required roles moved into the workflow and surfaced directly during approval submission. Existing attribute mappings remained supported.

The later team-led Horizon re-skin preserved the component architecture, states and options I had established in Glucose. A broad visual change could therefore happen without rebuilding the system from scratch.

The Editor direction modernised navigation, headers, toolbars, and action configuration while deliberately preserving the familiar workflow canvas and model.

The Hub experience kept process context beside a structured change list: owners could accept or ignore reliable automatic updates, coordinate remaining manual work, and inspect propagation decisions in History. The review surfaces shipped first, with the fuller History view following shortly afterwards.

The Hub-native loop keeps request configuration, recipient acknowledgement, and completion monitoring within the published-process experience.

The Task direction combined suite navigation with clearer intra-task movement, metadata, form hierarchy, and a consistent information panel.

When SAP alignment became the direction, I compared Glucose and Fiori across controls, layouts and compound components to identify where the existing structure could be preserved beneath a new visual language, particularly in the context of the Governance app.

The legacy task experience, app-wide prototype, and later Fiori direction show how shared structural patterns carried through the phased modernisation.

Required roles moved into the workflow and surfaced directly during approval submission. Existing attribute mappings remained supported.

When SAP alignment became the direction, I compared Glucose and Fiori across controls, layouts and compound components to identify where the existing structure could be preserved beneath a new visual language, particularly in the context of the Governance app.

The Hub-native loop keeps request configuration, recipient acknowledgement, and completion monitoring within the published-process experience.

The Editor direction modernised navigation, headers, toolbars, and action configuration while deliberately preserving the familiar workflow canvas and model.

The Hub experience kept process context beside a structured change list: owners could accept or ignore reliable automatic updates, coordinate remaining manual work, and inspect propagation decisions in History. The review surfaces shipped first, with the fuller History view following shortly afterwards.

The later team-led Horizon re-skin preserved the component architecture, states and options I had established in Glucose. A broad visual change could therefore happen without rebuilding the system from scratch.

The legacy task experience, app-wide prototype, and later Fiori direction show how shared structural patterns carried through the phased modernisation.

The Task direction combined suite navigation with clearer intra-task movement, metadata, form hierarchy, and a consistent information panel.

02 /

Archive

Ad2games

Selected earlier work from my time at Ad2games

I also created the Nevaly style guide. This snapshot combines several sections covering layout, buttons, inputs, forms, and developer-focused front-end component documentation.

A reporting and campaign-management interface for ComboStrike Insights, supporting advertiser workflows around campaign setup, KPIs, reporting, and analytics access.

A presentation framework and slide system for Ad2games, supporting reusable sales and client decks across campaign strategy, media mix, performance, and game marketing topics. Prior to this template framework, there was no unifying quality, structure or aesthetic to company presentations, which varied significantly depending on the author. The framework was hugely popular, and gained rapid adoption. I was able to extend and iterate as further presentation needs surfaced.

An influencer marketing dashboard for managing signed campaigns, platform channels, creator metrics, budgets, and campaign configuration within Nevaly.

A simple promotional landing page for Albion Online, presenting tiered packages, pricing, and a call-to-action. The background was actually animated. I designed and coded the page, but did not create or design any of the visual assets, which were provided by the publisher at the beginning of the project.

An influencer marketing dashboard for managing signed campaigns, platform channels, creator metrics, budgets, and campaign configuration within Nevaly.

A presentation framework and slide system for Ad2games, supporting reusable sales and client decks across campaign strategy, media mix, performance, and game marketing topics. Prior to this template framework, there was no unifying quality, structure or aesthetic to company presentations, which varied significantly depending on the author. The framework was hugely popular, and gained rapid adoption. I was able to extend and iterate as further presentation needs surfaced.

A reporting and campaign-management interface for ComboStrike Insights, supporting advertiser workflows around campaign setup, KPIs, reporting, and analytics access.

I also created the Nevaly style guide. This snapshot combines several sections covering layout, buttons, inputs, forms, and developer-focused front-end component documentation.

A simple promotional landing page for Albion Online, presenting tiered packages, pricing, and a call-to-action. The background was actually animated. I designed and coded the page, but did not create or design any of the visual assets, which were provided by the publisher at the beginning of the project.