bringing a brand back together

The Design System that unified SOS Children's Villages

With a presence in over 130 countries SOS Children’s Villages is a renowned international non-profit for child’s wellfare. Digify, established internally in 2002, focuses on developing innovative fundraising products to support the organization’s mission of building families for children in need.

HOW MANY: 40+ countries, 150+ Touchpoints with 5 themes

WHEN: March 2016 – today (8 years old)

WHO: A global team of 450 fundraisers + design practitioners

WHAT: SaaS Product Design, Front-end Development, UX/UI, Digital Fundraising

always in firefighting mode

The Before

Upon joining the organization, we faced a fragmented landscape with over 40+ and 150 instances utilizing custom products. The proliferation of custom solutions led to a high volume of change requests and inconsistencies across platforms, that included:

Part 1: The Kickoff


Part 2: Distribution

  • Crowdfunding Platform
  • Sponsorship App (PWA)
  • Gift card Generator
  • International DAM System
  • GDPR & CCPA Compliance
  • WGAC 2.1 Compliance
  • PageSpeed Insights 
  • Migrations & Non-functional updates
  • E-learning App (external)

the token-based design system

The Only Way Forward

To address the challenges posed by fragmentation and to bolster operational efficiency, we made a strategic decision to unify the organization’s digital presence. This involved consolidating disparate platforms and custom solutions into a cohesive ecosystem through the implementation of a comprehensive design system and theming strategy. 

By adopting this approach, we aimed to streamline processes, improve consistency across platforms, and facilitate more efficient management of digital assets and resources. This concerted effort was crucial in aligning the organization’s digital identity and reinforcing its commitment.

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

FĂĽge hier deinen Tooltip-Text hinzu

Poor design decisions are expensive

Why they chose me?

Having previously worked as a freelancer within SOS Children’s Villages and being a vocal advocate for design systems, my deep understanding of the organization’s needs and commitment to cohesive design principles made me the ideal candidate for the project. My immediate tasks were clear:

Stefan combined strategic and technical expertise to transform global fundraising operations at SOS CV. As lead SaaS product designer, he consolidated our fundraising software across 30+ countries, creating a unique digital shared service in the sector.

This brought major efficiency gains and improved international collaboration, enabling cross-country teams to work seamlessly across CMS, email, apps, and CRM systems. He ensured solutions met GDPR, accessibility, and PCI standards while navigating complex international requirements.

By aligning technology, compliance, and fundraising strategy, Stefan delivered lasting value, enhancing both operational excellence and the global reach of our mission.

July 1, 2016 – march 31, 2017

The Transformation

Over a period of approximately 8 months, I collaborated closely with SOS Kinderdorf Ă–sterreich, the brand owner – to implement the redesign initiative. Despite managing stakeholder requests from 4 continents, we remained focused on the goal of unifying the brand’s digital identity.

In order to enforce the adoption of the new brand identity we incorporated an isolated model of development where the driving force was the brand owner, which is not ideal, but in this particular case was the only reasonable way to move forward.

Deliverables:

Pilot integration: https://www.sos-kinderdorf.at/

New Brand book: Link

Challenges

⚠️ Unlike most CMS systems – Kentico comes completely RAW – which means that we had to develop something like Elementor or Webflow from scratch.

1. Stakeholder management

This challenge stemmed from the need for extensive discussions and negotiations to align diverse stakeholder perspectives on design decisions. With stakeholders spread across 40 countries, coordinating feedback and reaching consensus on design elements proved to be a time-consuming process.

2. Lack of Brand Assets

The absence of updated brand assets since the 80’s posed a significant challenge. This meant that we had to develop a cohesive design system from scratch, lacking modern brand guidelines or visual references, which required substantial research and creative interpretation.

3. Migrating legacy content

Migrating legacy content presented its own set of challenges, particularly ensuring that thousands of pages were migrated correctly while maintaining consistency with the new design system. This necessitated the development of legacy templates to accommodate existing content structures and formats, ensuring a seamless transition to the redesigned platform.

a brand that’s truly aligned

The CMS After

⚠️ Unlike most CMS systems – Kentico comes completely RAW – which means that we had to develop something like Elementor or Webflow from scratch.

Through strategic decision-making and collaborative efforts, we successfully unified SOS Children’s Villages International’s digital presence, enabling the organization to operate more efficiently and cohesively across borders. The impact of the redesign extended beyond marketing metrics, fostering greater satisfaction among editors and improving processes for faster delivery.

Front-End Backlog Reduction
0 %
Time-to-Market for Content
+ 0 %
saved on repetition
0 %
Stefan was on my team for 6 years, driving the Product Design for our global digital marketing platform in over 40+ countries in 4 continents. Stefan is apart from his web front-end skills (which are always synchronised with the pace of the industry and above he is always looking at coming trends to be implemented) a great communicator and networker.

End-to-end Research, design & development

The ultimate email template used in Emarsys, Salesforce & Microsoft Dynamics

The process of developing the email template that impacts 20 million users with 500 million emails delivered annualy

Summary

Build and distribute a new Template for all CRM systems

Develop a pixel-perfect email template design with various sections and colors that needed to be transformed into a responsive email template and integrated into Emarsys, Salesforce, MS Dynamics. A piece of cake, you’d say.

01

02

Problem Statement

Cross-Platform Support

The tricky part was that this template had to be fully implemented into the Emarsys, Salesforce or Microsoft Dynamics 365 marketing CRM across the whole SOS Children’s Villages Federation (70 countries, 250 teams). And to make the challenge even greater, the email template also had to be templated and fully editable in common native email builders. So, ended up with every heading, paragraph, button, color, picture, and link in this template being editable, plus having the ability to add/remove different sections within the prebuilt templates for:

  • Fundraising & Marketing
  • Marketing Automation flows
  • External Communication Teams
  • Intranet Communication
  • Thank you, confirmation & error emails for payment and non-payment forms
  • HR Responding Emails

Focus Points

Challenges

A. Cross Mail Clients Support

We all know that email templates are challenging to work with because of the code structure they use. In addition, every mail client (Microsoft Outlook, Apple Mail, Gmail) renders the code differently via its own style rules. Therefore, the code has to support all specific requirements to look identical on all mail clients.

B. Responsive design

Responsiveness is almost impossible due to the cross-mail client support and the limited CSS rules.

C. Implementing in third-party-tools

I had to use the Emarsys, Kentico, MS Dynamics and Salesforce syntax to implement our template and make it modular and editable for the interactive web builders.

03

04

tested over time

MJML Base

The template was developed with MJML as a component-based design system.

  • 7 x Headers
  • 5x Footers
  • 40 x components
  • 15 x templates

 

Alongside the template, I started facilitating workshops and developing an internal e-learning platform to build knowledge capacities within the teams of email editors for template localization.

  • Editing existing templates
  • Building new templates from existing campaigns
  • Creating custom Emarsys controls with own syntax
  • Tracking & marketing automation
CRM Before
CRM After

my work in numbers

The Real Impact

With this project, I provided the digital marketers in the organization with more flexibility, eliminating their need to work with designers and developers to create an email template for their email marketing campaigns. Thus, they can reach more people more quickly and easily. Plus, it saves a lot of resources by freeing up more of the designers’ and developers’ time across the organization.

Knowing that this template will influence more than 100 million people makes me proud of being involved in the project and for earning our client’s trust.

Users
0 M
Emails
0 M
Countries
0
I have worked with Stefan when he was a SaaS Product Manager and Digital Fundraising Advisor at SOS Children's Villages. Stefan is a creative mind with a particular focus on user orientation and a special attention to creative aspects in web design. He has the improvement of web applications in focus at all times.

one design system to rule them all

A Design System for all forms

We needed a design system to organize and provide detailed specifications to the developers’ team to organize their donation journey in 40 countries and across 70 touchpoints – Web, App, PWA.

a decision postponed for many years

The Before

  1. Fragmented Development: Without a unified Design System, development across 40 countries became fragmented and ad-hoc moreso when it comes to payment and process forms

  2. Running in circles: Lack of standardization led to reinventing forms, causing a larger development backlog.

  3. Limited Knowledge Transfer: Absence of a centralized system hindered technology sharing between teams, resulting in inefficiencies.

  4. Poor UX: Inconsistent designs and functionalities led to a subpar user experience, potentially deterring donors.

  5. Reduced Conversion: These issues culminated in decreased conversion rates on donation forms, impacting fundraising efforts.

Features and Enhancements:

The Forms After

The results of the transformation were profound. SOS Kinderdörfer Weltweit’s digital platform emerged with a cohesive, modern design that resonated with users and effectively communicated the organization’s mission. Content management became more intuitive, empowering staff to deliver timely, impactful messages to their global audience.

Accessibility Compliance
0 %
Less Bounce Rate
0 %
Reached Checkout
+ 0 %
I’ve worked closely with Stefan on a bunch of software projects with a global footprint. One thing I can say is that he’s a Design Systems Wizard. If you’re a software developer as I am you should look no further than him when it comes down to SaaS product design, building and integrating design concepts seamlessly into front-end and CMS architecture. His ability to negotiate and facilitate multiple major stakeholders feedback into a single design system is unparalleled. He’s a great addition to any SaaS team.

Let’s create something great together.

My Process

1. Ideation

Surface real problems, not just feature requests.

Capture user signals (ideas, opportunities, warnings, errors) and convert them into tightly framed problem hypotheses for quick validation.

Key deliverable: tagged idea backlog + 1-page problem brief.

UX boost

idea generation

opportunity

error

2. Business Validation

Make sure the idea matters to users and the business.

Quickly test value and risk: size demand, surface downstream impacts (ops/legal/support), and run lightweight experiments (landing page, concierge MVP, etc.) to validate willingness-to-pay or behavior change before engineering.

Deliverables: business brief (assumptions + TAM snapshot), simple experiment plan, go/no-go recommendation.

validation

valuation

risk assessment 

3. Tech Buy-in

Turn validated value into a predictable engineering plan.

Engineers translate the validated case into a pragmatic technical approach: feasibility checks, data/API contracts, MVP scope, acceptance criteria, and a phased rollout (feature flags / canary / incremental migrations). Align on risks, performance and security requirements so delivery is predictable and debt is managed.

Deliverables: one-page tech spec + sequence diagram, backlog tickets with acceptance criteria, rollout & mitigation plan.

Feasibility

alignment

flagging

4. Stakeholder Buy-in

Secure resources, remove blockers, and de-risk execution.

We synthesize ideation, validation, and technical alignment into a concise decision pack that answers: Why now? What is the financial impact? Who does what? How do we mitigate risk? The pack includes an executive one-pager, ROI/payback scenarios (conservative → aggressive), a resourcing map (teams, capacity), and a phased milestone plan with KPIs. In the decision review, we anticipate objections (cost, scope, system impact) and offer mitigations (phased pilots, lighthouse customers, feature-flagged rollouts). The goal is formal sign-off.

Deliverables: executive one-pager, ROI model, approved resource allocation, milestone sign-off + communication plan.

Success metrics: time to funding decision, % of requested resources granted, milestones met vs committed, realized vs projected impact at Q1/Q4.

pitch

approval

budget

Delivery
Development