Speaker: Simon Truckenmüller, Mercedes-Benz.io Title: Developing the cultural API between holacractic and non-holacratic organizations Event: Holacracy - Experience first-hand self-organized working (Meetup on July 18th 2018 at Siemens in Munich)

1. Developing the cultural API between holacractic and
non-holacratic organizations

2. About me
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 2

3. About Mercedes-Benz.io
Mercedes-Benz.io
Started in 2015 with
holacracy as organisational
framework.
State of a supplier.
Independant, autonomous,
self-organized. Easy to set
up the own framework.
2016 agile, scrum as
operational mode
06/2017 mb.io becomes
100% subsidary of Daimler
AG.
Framework light for mb.io
The responsive
organisation stays.
Digital house, joint
operations.
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 3
2015 2016 2017 2018
2 9030 18
0
250
DAG buys CINTEO
and mb.io was born
Lisbon
Berlin
founding of
CINTEO
Stuttgart

4. About Mercedes-Benz.io
Mercedes-Benz.io
Started in 2015 with
holacracy as organisational
framework.
State of a supplier.
Independant, autonomous,
self-organized. Easy to set
up the own framework.
2016 agile, scrum as
operational mode
06/2017 mb.io becomes
100% subsidary of Daimler
AG.
Framework light for mb.io
The responsive
organisation stays.
Digital house, joint
operations.
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 4
founding of
CINTEO
2015 2016 2017 2018
2 9030 18
0
250
DAG buys CINTEO
and mb.io was born
Lisbon
Berlin
Stuttgart
...and what we deliever.
Digital Commerce
Workbench
OneWeb
Insights factory
collection shop
online vehicle
sales
marketplace
connect
platform
accessories
shop
GPMe
seller center
vehicle search test drive
configurationsfamily
waiting phase
Dealer locator
financial calculator
Foundry
Mercedes me
integration
UX /
CX
Dev
Rollout
PO
QA
Analytic
s
PM
...

5. How to merge waterfall, agile, responsive, hierarchy, stakeholders,
projects, products,...
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 5

6. 2015
Fully independent organisations
work in waterfall and agile
projects managed by CINTEO.
The DAG is working via
represantitives.
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 6
CINTEO
supplier
supplier
supplie
r
supplie
r
supplie
r
project 1
project 3 project 4
project 2

7. 2016
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 7
CINTEO
supplier
supplier
supplie
r
supplie
r
project 1
project 3 project 4
project 2
product2
product1
product 3
Suppliers become less. Some
start to work directly with DAG
colleagues.

8. supplie
r2017
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 8
mb.io
supplie
r
product 9
product 8 product 7
project 2
product 2
product1
product 3
DAG starts to build swarms and the joint operations starts.
product 5
product 4
product 6
product 10

9. 2018
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 9
mb.io
product 9
product 8
product 7
project 2
product 2
product1
product 3
Products become part of the organisational structure.
product 5
product 4
product 6
product 10

10. Step by step. It is a relation.
And relations need communication and continous engagement.
• Integration of
DAG colleagues
by creating and
assigning
dedicated roles
in circles
• Integration of
suppliers into
glassfrog
• Introducing the
company
advocats
• Holacracy
ambassadors
offer regular info
and training
events
• The frequent „big
sprintchange“
(we call it
Boxenstop)
across all teams
and
organizations
• dedicated
escalation roles
• Integration of DAG colleagues by creating and
assigning dedicated roles in circles
• Integration of suppliers into glassfrog
• Introducing the company advocats
• Holacracy ambassadors offer regular info and
training events
• The frequent „big sprintchange“ (we call it
Boxenstop) across all teams and
organizations
• dedicated escalation roles
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 10

11. Integration of DAG colleagues by roles in our framework
• Integration of
DAG colleagues
by creating and
assigning
dedicated roles
in circles
• Integration of
suppliers into
glassfrog
• Introducing the
company
advocats
• Holacracy
ambassadors
offer regular info
and training
events
• The frequent „big
sprintchange“
(we call it
Boxenstop)
across all teams
and
organizations
• dedicated
escalation roles
• Did not really work until today
• Different scheduling of frequent meetings
• Talking vs. doing
• People outside mb.io are often other directed
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 11

12. Integration of suppliers into glassfrog
• Integration of
DAG colleagues
by creating and
assigning
dedicated roles
in circles
• Integration of
suppliers into
glassfrog
• Introducing the
company
advocats
• Holacracy
ambassadors
offer regular info
and training
events
• The frequent „big
sprintchange“
(we call it
Boxenstop)
across all teams
and
organizations
• dedicated
escalation roles
• Due to legal reasons only as stand in
• They join „tacticals“ via represantitives
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 12

13. Introducing the company advocats
• Integration of
DAG colleagues
by creating and
assigning
dedicated roles
in circles
• Integration of
suppliers into
glassfrog
• Introducing the
company
advocats
• Holacracy
ambassadors
offer regular info
and training
events
• The frequent „big
sprintchange“
(we call it
Boxenstop)
across all teams
and
organizations
• dedicated
escalation roles
Purpose
• Safeguarding the Mercedes-Benz.io
principles, culture and values and act as a bi-
directional membrane to the external world
Accountabilities
• Creating transparency regarding external
tensions for Mercedes-Benz.io and regarding
internal tensions to the external world (i.e.
Daimler AG)
• Communicating and fostering awareness of
Mercedes-Benz.io principles, culture and
values to external world
• Anchoring the Mercedes-Benz.io values in the
partnership with the Daimler AGDeveloping the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 13
Company
Advocate

14. Holacracy ambassadors offer regular info and training events
• Integration of
DAG colleagues
by creating and
assigning
dedicated roles
in circles
• Integration of
suppliers into
glassfrog
• Introducing the
company
advocats
• Holacracy
ambassadors
offer regular info
and training
events
• The frequent „big
sprintchange“
(we call it
Boxenstop)
across all teams
and
organizations
• dedicated
escalation roles
• 8 holacracy ambassadors across all locations
• executing frequent surveyes
• onboarding of external colleagues to
holacracy
• Being the main contact for all holacracy
related questions
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 14

15. The frequent „big sprintchange“ (we call it Boxenstop) across all
teams and organizations
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 15

16. dedicated escalation roles?
• Hierarchies demand escalation points
• Our hierarchy is role based
• So we give „them“ escalation points in our role
model according to the accountabilites
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 16
Product

17. dedicated escalation roles?
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 17
Product
UX
Designer
Stake Holder
I don‘t like
the blue
button
I‘m gonna
tell you
why we
did it

18. dedicated escalation roles?
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 18
Product
Product
Owner
E?
Why does
it take so
long?
I‘m
responsible
for the
priorization

19. Enterprise
Architect
dedicated escalation roles?
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.2018 19
Product
IT
Consultan
t
We urgently need to
solve that
impediments with
the backend
systems
...we have to
do that
together
with...

20. Thank you. Feel free to approach me for more
exchange.
Developing the cultural API between holacractic and non-holacratic organization | mercedes-benz.io | 18.07.201820
Don‘t stop adapting. Change
continuosly.