Dr. Samuel Reeb, smiling, in a three-quarter profile, holding his glasses
Founder of Witnity

Dr. Samuel Reeb

Samuel Reeb combines academic work on collaboration, organisational development and knowledge work with practical experience in process design, software implementation, automation and consulting.

Science shaped how I think. In practice, I tested and extended it. With Witnity, I bring both together.

A perspective shaped by different contexts.

Understanding and steering knowledge

Knowledge management and strategic steering were an early focus – among other things in a master's thesis on knowledge controlling.

Rethinking collaboration and organisation

In research and his PhD, the focus turned to how collaboration, organisational conditions and strategic development interact.

Shaping change in practice

Later roles added process automation, software implementation, consulting and product work – and with that, the practical translation of business requirements into work processes and technology.

Selected practical experience

In an earlier role at Deutsche Bahn, Samuel Reeb supported the introduction of new software as a multiplier within one organisational unit – close to the everyday work of the people who used it.

Across different professional contexts, Samuel Reeb automated recurring reporting, review, registration and reminder workflows.

In IT consulting, Samuel Reeb worked directly with clients on business requirements. In product management, prioritising technical and business topics was added.

Software implementation & everyday work

In an earlier role at Deutsche Bahn, Samuel Reeb supported the introduction of new software as a multiplier within one organisational unit – close to the everyday work of the people who used it.

Automating recurring work

Across different professional contexts, Samuel Reeb automated recurring reporting, review, registration and reminder workflows.

Connecting subject-matter expertise and technology

In IT consulting, Samuel Reeb worked directly with clients on business requirements. In product management, prioritising technical and business topics was added.

Different experiences. One shared perspective.

What connects these different stages is a focus on how knowledge, processes, collaboration and technology actually interact in everyday work.

Talk about your situation