A simplified version of Enterprise Architecture can be a useful tool in developing and implementing innovation plans. I presented this talk at Software Architecture London in 2018
2. Code of Conduct
A primary goal of Mozilla's developer outreach is to be inclusive to the largest number
of participants, with the most varied and diverse backgrounds possible. As such, we
are committed to providing a friendly, safe and welcoming environment for all,
regardless of gender, sexual orientation, ability, age, ethnicity, socioeconomic status,
and religion (or lack thereof).
This Code of Conduct outlines our expectations for all those who participate in our
conference community, as well as the consequences for unacceptable behavior.
We invite all those who participate in our events to help us create safe and positive
experiences for everyone.
Please find the full text here: https://mzl.la/devroadshowcoc
3. Enterprise
Architecture as
an Astrolabe to
Guide Innovation
1. Who is Mozilla and why do we need to innovate?
2. Where are we now? How do we know?
Let’s see what an EAAstrolabe could be
3. Where do we want to go? How
do we get there?
A journey of innovation, guided by our tools, driven
by our techniques
“
“But groundless hope, like unconditional love, is the only kind worth having….”
9. What’s an astrolabe?
The mater (information disk) and
alidade (ruler) on the back are used
for ascertaining date, time, etc….
The rete (pointers) and
plates reflect what the
viewer can see today
See real astrolabes
from the Islamic
world at the British
Museum! Check out
their blog, with a
demonstration video:
https://blog.britishmuseum.org/
seeing-stars-astrolabes-and-the-
islamic-world/
10. How can we make an EAAstrolabe?
• Plates- The City Map shows where we’re
heading, our view of the stars, at multiple levels
• Rete- A time-based view could change colors as
we move forward on our journey
• Mater- A visualization of our evolving business
model and posture as of the date in question
• Ruler- A simple way to show time progress
13. Enterprise Architecture is People!
• New Mozilla City Map application in
ServiceNow associates every item with people
and groups, for current and future state
• Every capability-product-service has an owner
and associates
• Team is empowered to create their long-term
vision and to roll it up to other teams
14. Capturing Future State
• The City Map needs to be a time-based view
• Capabilities need a 3 yearvision, Products a 1
year roadmap, Services are generally reactive
• Until we create space for imagination, we can’t
capture and share useful future views
15. How can we use this to guide our journey?
Creating the future for Mozilla
16. Our shared mission builds trust
and implies connection
Blogging, lunch conversations,
TRIBE sessions
Innovation takes time and mental
space. Some teams offer 10%
time, but it’s not consistent
Mozilla All Hands,GitHub,
Discourse, other collab systems
Culture of Experimentation
program teaches scientific rigor
for experiments
17. Our business model needs to evolve
• The desktop browser is our lifeline but future
growth is limited- we’ve learned
• New ideas could come from anywhere- staff,
volunteers, product teams, anyone with a vision
• Mozilla is always evolving- Firefox OS, IoT, etc…
18. Innovation from Experimentation
Drives Mozilla Forward
• Culture of Experimentation seeds innovators with techniques
to give rigor
• COE cohorts provide trusted support to enable success as well
as quick educational failure
• Experiments are aligned with our capabilities and based on
products- they fit in the map
19. How do we move forward and innovate?
Innovation Tools That Can
Drive Our Evolution
20. Innovation is a Game- so play!
• Thing From The Future- a card game that gets
the imagination going
• Hackathons- with enough structure to support
those who need it, but time for free expression
as well
• Models of Impact- a game that inspires teams
to consider capabilities, mission impacts, and
revenue for the mission
21.
22.
23. Know the
next hits!
And archive
the oldies.
Catalog
current
capabilites
Explore,
Experiment,
Expand
Research!
Consider
impact models.
Remix
capabilities
What can we
do today?
What will we be able
to do in the future?
How can we impact
the mission with our
capabilities?
Is this remix
a viable
product?
Innovate Like A DJ!
Mozilla can use our Capabilities like a DJ uses vinyl records.
We play around with different combinations, and anticipate what’s
coming and what the crowd wants, and after we deliver the set, we
repurpose what we learned to make the next set even better!
Here’s one example (XR Studio) of how this can work.
New capability:
Mixed Reality and
Speech/Language-
based assistants
Impact: Improved
social and
economic mobility
for often
marginalized
groups and
individuals.
Remix: A
Community Space
for Mixed Reality
work.
MVP: XR Studio!
Now we can play the Product
Owner boardgame and harvest
our learnings.
What can we recycle
and repurpose from
this effort?
Capability: WPR’s
Community Spaces.
24.
25. Come join the ride! https://jobs.mozilla.org
Michael Van Kleeck: mvk@mozilla.com or LinkedIn
Music podcast at www.mvk.net/officehours
Make the web more open! Be a part of MDN:
developer.mozilla.org