Factter frame with building blocks, symbol of the coherent working model.

Approach.

Factter’s approach redesigns how organizations work: structure and culture, the visible side and the undercurrent. Every track starts from one coherent working model, from organization design through leadership and teams to HR processes, HR systems and AI. The goal is always the same: an organization in which change doesn’t pile up but lands.

Starting point

One coherent working model

Organizations are not loose parts. Those who only adjust the structure see leadership and behaviour spring back to the old. Those who only work on culture collide with a structure that keeps rewarding the old behaviour. That is why Factter works with one coherent working model, grown out of the tradition of innovative work organization. It reads an organization in coherence, from intent to setup.

The model asks four core questions. Performance: what does this organization need to achieve? Organization: what kind of organizational model is needed for that? Relations: what does result-oriented collaboration mean for each unit? And jobs: what is the content of each job, and what do we expect from people?

Every core question is viewed from two lenses: culture and structure. That gives every question two dimensions. For performance: vision and process. For organization: leadership and macrostructure. For relations: team and microstructure. For jobs: individual and systems. Under systems also live HR processes, HR systems and AI applications.

In the middle of the model stands what all this serves: a future-proof organizational model. That must align with the strategic priorities (performance), allow efficient coordination and alignment (organization), avoid misunderstandings and information loss (relations), and give people perspective to learn and grow (jobs).

And AI runs as a design variable through the whole model. AI is more than an application under systems: it shifts what performance requires, who decides what, how teams collaborate and what a job entails. That is why AI touches all four core questions and both lenses; further down this page we work that out.

In every track the whole model is on the table, but not everything with equal weight: where the change load piles up, that is where the emphasis lies. That makes the model not a roadmap but a compass.

CultureStructure
01

Performance

  • Vision
  • Process
02

Organisation

  • Leadership
  • Macrostructure
Goal

A future-proof organisation model

03

Relations

  • Team
  • Microstructure
04

Jobs

  • Individual
  • Systems
AI runs as a design variable through the entire model

Extended working-model visual

Here’s how you begin: the offer →

Design principle

Designing around the work, not around functions

Stream-based organizing means an organization is built around its work streams: the path a customer request, a case or a product travels from start to finish. Teams get a recognizable, complete piece of that stream, with the room to adjust what touches their work. The alternative, a functionally divided organization, cuts up the work per specialism, so every stream runs through many departments and every change becomes a coordination project.

The difference shows itself most sharply during change. In a divided structure every initiative crosses departmental boundaries: systems here, processes there, decisions elsewhere. Change has to travel through the whole organization and piles up with the same teams, the same scarce roles, the same decision layers. In a stream-based structure the same change lands locally: the team that carries the stream adjusts itself.

That is why Factter designs according to three principles. Organize work around streams instead of functions. Place decision space as close to the work as possible. And keep coordination light: alignment that adds value, instead of meetings that have to glue departments together.

Why now

AI as a design variable

We treat AI in every design as a full design variable, for three reasons that make AI different from earlier technology waves.

1

Breadth

AI doesn't touch one department but all of them at once. In a divided structure every AI application crosses departmental boundaries: data here, process there, decision elsewhere. Every application becomes a coordination project.

2

Continuity

AI change has no end date: models and capabilities shift monthly. An organization that handles change as a project (program, steering committee, rollout, done) falls structurally behind. Absorbing must be a built-in capacity.

3

Depth

AI changes not just the tools but the work itself: which tasks stay human, where judgment is needed, who decides. That is work organization, and therefore a design question.

Concretely that means: in every redesign we divide the work between people and AI. Which tasks can AI take over, which become stronger with AI, and where does human judgment remain the norm? Which roles and teams belong to that division, and how does the design keep space to redistribute when the AI capabilities shift again?

Good AI governance comes with that: agreements about what AI may, who oversees and where decision space sits. Good AI governance makes AI usable by placing decision space close to the work, within clear frames; heavy approval layers achieve the opposite. Factter helped build that governance practice from the inside in large organizations, from policy and decision rights to the shop floor.

AI in practice: human-centred digitalization →

Foundation

Half a century of organization science

Factter’s approach is not a collection of our own inventions, but rests on half a century of organization science. Four traditions carry the working model.

The design tradition that shows how the structure of the work determines how agile, workable and productive an organization can be. This is where the principles of stream-based organizing and room to adjust come from.

Evidence-based at Factter means: these insights are the touchstone of every design, not a label on the website. Where the design deviates from them, the design must justify itself.

Six working principles

Together with your teams, not over their heads

Six work principles apply in every track and every mandate.

  1. 01

    Design with the people who do the work

    The teams who will work in the new structure design along. Not as a buy-in trick, but because they know the work and because co-designing is the first exercise in room to adjust. What emerges is a shared result that everyone benefits from, and not a change imposed from above.

  2. 02

    Diagnosis before design

    We don't start with a solution but with the question of where the change load piles up and why. What we can't substantiate, we don't recommend.

  3. 03

    The whole model on the table, the emphasis where it hurts

    Every track looks at the entire working model in coherence, and invests deepest where the analysis points.

  4. 04

    In two directions

    What is decided above must be workable below; what happens on the ground must return to the table where decisions are taken. Short lines in both directions are not a meeting culture but a design requirement: without that feedback, decisions get taken on a picture that no longer holds.

  5. 05

    Built to continue without us

    The goal is an organization that absorbs the next change on its own. We transfer the way of looking, so the capacity stays in-house.

  6. 06

    The shop stays open

    Redesigning happens while the work continues. We start where the organization already stands, safeguard the daily operation during the transition, and close with what has been learned: that way the change also stays in place after the track ends.

See how you begin →

Frequently asked questions

That structure and culture are tackled together, in one coherent working model. A new structure without work on leadership and teams springs back; culture work without structural change collides with an organization that keeps rewarding the old behaviour. Integral means: the whole working model in coherence, with the emphasis where the analysis points.

Being able to handle change is not a character trait of organizations. It is a design choice.

See the offer →