Inglebert Christiansen's Portfolio

Redefining Systems Engineering

I worked alongside Frazer Nash Consulting's Systems Engineering team to design FNSIGHT — a centralized knowledge hub that helps FNC staff retain, manage, and share project knowledge across the organization.

Team:

Timeline:

Role:

Tools used:

4 Designers + FNC Stakeholders

3 Months

UX Researcher, UI Designer

Figma

Redefining Systems Engineering

Team:

Timeline:

Role:

Tools used:

4 Designers + FNC Stakeholders

3 Months

UX Researcher, UI Designer

Figma

4 Designers + FNC Stakeholders

3 Months

UX Researcher, UI Designer

Figma

Redefining Systems Engineering

Team:

Timeline:

Role:

Tools used:

4 Designers + FNC Stakeholders

3 Months

UX Researcher, UI Designer

Figma

The Challenge

Systems engineering and systems assurance are the invisible scaffolding behind successful projects across sectors Yet despite their importance, many clients and internal members have a vague or construed understanding of it’s value.

How might we develop a shared knowledge of systems engineering for internal FNC staff such that they are confident in explaining its benefits, deliverables and methodologies to external clients?

In other words….

Our Approach

Being Comfortable with Uncertainty

After initial stakeholder meetings, we found ourselves with dozens of potential insights but no clear direction. Instead of rushing to solutions, we sat with the uncertainty and started finding patterns through affinity diagrams. This patience revealed the core issue lies in knowledge access and sharing.

How do we balance flexibility and structure

Knowledge management

Intangible KPI

Difficulty communicating to other industries

Technical nature of the work

Reluctance to internal change

No team that manages information between projects

Communicating the value of systems engineering in a universal language

Finding ways for openly sharing information regardless of position in the team.

Building adaptable solutions that respond to complexity and and future uncertainty.

Addressing the need for knowledge sharing and retention inside the organization.

How do we balance flexibility and structure

Knowledge management

Intangible KPI

Difficulty communicating to other industries

Technical nature of the work

Reluctance to internal change

No team that manages information between projects

Communicating the value of systems engineering in a universal language

Finding ways for openly sharing information regardless of position in the team.

Building adaptable solutions that respond to complexity and and future uncertainty.

Addressing the need for knowledge sharing and retention inside the organization.

Communicating our Findings

Further research approach combined qualitative stakeholder interviews with journey mapping to understand both current pain points and future opportunities. Working directly with FNC's systems engineering team allowed us to ground our design decisions in real organizational challenges.

Stakeholder Interviews

10+

Projects analyzed between departments

180+

Total hours of research

We went from the current user journey

To our proposed user journey

Revamping FNC's Relationship with Knowledge

FNSIGHT is a centralized knowledge management system concept that would enable FNC to retain, manage, and share project knowledge across the organization. The platform transforms isolated project information into an accessible, searchable database that supports both current work and future business development.

Project Database

Searchable archive of 3,500+ past projects with AI-powered summaries, team information, and outcomes. Engineers find relevant precedents in seconds instead of hours.

Network Map

Interactive visualization of FNC's professional network across industries and organizations. Identifies partnership opportunities and subject matter experts.

Projects Page

A user-friendly project page accessible to all, allowing new joiners to effectively bridge the knowledge gap and contribute more information to the project.

Performance Report

Real-time analytics tracking knowledge base adoption, contributions, and usage patterns. Helps leadership measure system value and identify gaps.

Design Considerations

Microsoft Ecosystem Integration: Designed to work alongside FNC's existing tools (Teams, SharePoint) rather than replace them, reducing adoption friction

‍Progressive Disclosure: Complex project information organized in digestible sections to avoid overwhelming users with technical details

‍Accessibility Standards: Designed to meet WCAG 2.1 AA standards with high contrast ratios and full keyboard navigation support

‍Scalability: Information architecture designed to handle 1000+ future projects without performance degradation

Key Learnings

Domain expertise isn't required — curiosity is

I was initially intimidated by systems engineering terminology and complex technical processes. However, I learned that asking "naive" questions actually helped FNC clarify their own thinking. Not being the expert forced me to design for true clarity rather than assuming knowledge.

Stakeholder buy-in matters more than pixel perfection

We spent 60% of our time in workshops with FNC stakeholders and only 40% designing. This ratio felt uncomfortable at first, but it ensured we built something they'd actually champion internally. Direction first, design later became our mantra.

Internal tools require different validation approaches

Internal enterprise tools are measured differently from consumer apps, and their impact isn’t always immediately visible. We had to rethink what success meant, focusing less on engagement metrics and more on how well the system fit into existing workflows and supported real productivity.

Home

Playground

About

Resume