Organizational Architect · Vienna, Austria

Designing the invisible architecture of organizations

Most companies have a strategy. Few deliberately design the structural systems that determine how that strategy actually plays out.

Who makes which decisions. Who sees which information. How responsibilities are distributed. What behaviors incentives reinforce. And how technology supports or constrains the work.

That structural layer is what I call organizational architecture.

Core Idea

Architecture over accident

Strategy describes intent. Culture describes behavior. But between intent and behavior lies structure: the mechanisms that determine who knows what, who decides what, and how work flows through the organization.

Most companies treat this structure as an afterthought. Yet it quietly shapes almost every outcome — from coordination speed to decision quality to the success or failure of new systems.

I’ve spent my career at the intersections — where ERP logic meets team behavior, where process design meets human motivation, and where stated values meet actual decisions. Most people who work on organizations approach from one side: the technical, the cultural, or the strategic. I work where they meet.

Definition

What is Organizational
Architecture?

Organizational architecture is the design and analysis of the structural systems that shape how an organization operates.

It includes the mechanisms that determine how decisions are made, how information flows, how responsibilities are distributed, and how work is coordinated across people and technology.

Strategy defines direction. Culture describes behavior. Architecture defines the structure that produces both.

Decision structures
Information flows
Incentive mechanisms
Role distribution
Coordination mechanisms
Technology systems

Framework

The Layers of
Organizational Architecture

Five interacting layers shape how organizations decide, coordinate, and operate.

Decision Architecture

Authority, ownership, escalation

Defines who decides what, where decisions accumulate, and how trade-offs are resolved when priorities compete.

Information Architecture

Visibility, access, flow

Shapes what people can see, what remains hidden, and how knowledge moves across teams, functions, and levels.

Role Architecture

Responsibilities, interfaces, coordination

Clarifies responsibilities, handovers, and the structural relationships between roles that make coordination possible.

Incentive Architecture

Signals, reinforcement, trade-offs

Reveals which behaviors are rewarded, tolerated, or quietly discouraged in practice, beyond stated values.

Technology Architecture

Support, constraints, enablement

Shows how systems enable work, shape choices, and create operational constraints across the organization.

Experience Context

Working at the intersection of
systems and organizations

My perspective on organizational architecture comes from years working in environments where getting it wrong has real consequences — where structural systems directly shape operational outcomes.

I currently work in customer-facing operations at a mid-sized ERP software company, across key accounts, delivery teams, and internal organizational development. The work sits at the intersection of ERP systems and organizational processes, operational workflows and technology, and cross-functional coordination in complex environments.

Across projects and organizations, the same structural patterns tend to appear: unclear decision ownership, fragmented information flows, incentives that contradict stated goals, and systems that are technically sound but organizationally unsupported.

These are not primarily cultural problems. They are architectural ones.

ERP systems & organizational processes
Operational workflows & technology
Cross-functional coordination
Technology-driven process design
Organizational change

Research

A body of work with
a clear thread

Two master’s theses, five years apart, approached the same underlying question from different angles: how structural systems influence behavior and decision-making inside organizations.

2020 · Innovation & Technology Management

Why people don’t trust what they don’t yet understand

Research Focus

Technology adoption and acceptance, using autonomous vehicles as a case study.

Key Insight

Trust and perceived control influence adoption more strongly than technical performance. Intention to use and actual preference are separate phenomena.

Implication

Technology adoption is shaped less by technical capability alone than by decision structures, visibility, and perceived control.

2025 · Work & Organizational Psychology

Skill visibility and development in software organizations

Research Focus

How mid-sized software companies can visualize and develop team capabilities using gamification.

Key Insight

Organizational knowledge about who can do what exists almost entirely in managers’ heads. This is a structural visibility problem, not a tools problem.

Implication

Systems are more likely to succeed when they make progress visible and connect individual development to organizational needs.

What appears to be a technology problem is often a structural one.

Ideas in Progress

Observations on
structural behavior

A longer-term effort: developing a more coherent body of thinking about how organizations work at a structural level.

Why change fails structurally, not culturally

Most failed change initiatives are diagnosed as communication or culture problems. The people weren’t on board. The message wasn’t clear. Leadership didn’t show enough conviction.

These explanations are rarely wrong. They are also rarely primary.

Behind most failed change lies a simpler fact: the existing structure made the new behavior improbable before anyone was asked to adopt it. Decisions still accumulated at the old bottleneck. Incentives still rewarded the old pattern. Information still flowed through the old channels. The new work had to happen in the gaps between all three.

Culture does not resist change on its own. Structure resists it — and culture reflects that resistance back.

The more useful question is not how to get people on board, but what would have to be structurally true for the new behavior to be the path of least resistance.

That is an architectural question, not a communication one.

Also being explored

Decision gravity in organizations — why certain decisions accumulate at certain points
Structural causes of coordination failure
Technology systems as organizational architecture
The relationship between ERP systems and decision design

In conversation Managementdialog Podcast, Episode 8 — On change, structure, and why organizations resist transformation · April 2026

In practice 44up — Making the structures of a market visible rather than assumed · DACH food retail

Get in touch

For thoughts,
exchange, or resonance

This space is primarily a place to develop and share ideas. If these thoughts resonate with you or connect to challenges you’re thinking about, feel free to reach out.

hello@floriantomasin.com LinkedIn