6. Formal rules and procedures don’t have a
predetermined effect on people’s behavior.
Rather, people actively interpret rules and use
them as a resource to fulfill their goals. What
matters are not the rules, but the ways people
use them.
Morieux, Yves. Six Simple Rules (p. 21). Harvard
Business Review Press. Kindle Edition.
6@kvantomme -
7. 7
Make you curious about:
1. Systems thinking
2. Complex Adaptive Systems
3. The role of APIs in Digital
Transformation
4. The role of devportals in Digital
Transformation
@kvantomme -
Goals of this
session
12. From tightly
integrated value
flows, companies
need to become
value networks,
rerouting around
bottlenecks
towards
constantly
evolving value
sources
12@kvantomme -
13. 13
● Agile transformations
● DevOps
● Self-organizing teams
● InnerSourcing
● APIs
@kvantomme -
One goal many
transformations
22. COMPLEXITY
22
Complexity arises when a set of
agents have the right level of:
-Interconnection
-Interdependence
-Diversity
-Adaptivity
@kvantomme -
26. Complex
Adaptive Systems
are a group of
interacting
agents, that adapt
to complexity in
the environment
with complex
adaptive
emergent
behaviour
26@kvantomme -
33. How to adjust
to our new
environment?
33
1) Cooperate to remove friction
Appropriate intermediate levels of the
complexity parameters:
2) Interconnectedness
3) Interdependence
4) Diversity
5) Adaptivity
@kvantomme -
35. 1. Improve DX to improve
customer experience.
35@kvantomme -
36. Removing
friction
36
1. Developer eXperience is achieved
through dialogue not through top
down rules & governance
2. Developer eXperience can’t be
reached without adjustment costs: to
really collaborate fully, respectful
conflict is essential
@kvantomme -
38. Inter-
connection
38
1. Build as little devportals as
possible
2. Strongly encourage reuse, but
remain curious about exceptions
@kvantomme -
39. 3. Use APIs to engage with
more diversity
39@kvantomme -
40. Diversity
40
1. Make internal diversity available to
the whole organisation
2. Build an API partner platform to
benefit from external diversity
3. Don’t try to standardize everything
but embrace healthy diversity
@kvantomme -
41. 4. Create loosely coupled
interdependence through
APIs
41@kvantomme -
42. Inter-
dependence
42
1. Ideally APIs are constrained in such a
way that they don’t allow you to fail
2. But they are open enough to allow for
surprising applications
3. API consumers should be able to
influence API design and capabilities but
not dictate them
@kvantomme -
43. 5. Use APIs as a boundary
behind which teams can adapt
43@kvantomme -
44. Adaptivity
44
1. Be careful with API versioning, but allow
for change
2. Clearly communicate about API versions
on your devportal
3. Integrate documentation into the
development process to keep docs in
synch with changes to the API
@kvantomme -
45. 1. Improve DX to improve customer experience.
2. Increase interconnection through APIs.
3. Use APIs to engage more diversity.
4. Create loosely coupled interdependence
through APIs.
5. Use APIs as a boundary behind which teams
can adapt.
45@kvantomme -
CAS through APIs & Devportals