On 14th of May 2019 we had our inaugural meeting of the DAIRDUX Alliance. An Alliance to co-create and knowledge share to empower organizations with an analog legacy to become Data AI ready in operations and put AI in production.

In the room we had some massive experience and expertise from Big Corporates in Europe, super experts on Open source on Cloud data platforms, Machine Learning and AI, from niche consultancies, thought leaders and academia. Industries represented from Banking, Insurance, Telco, Energy, Energy Grid Operator (TSO) Mining, Manufacturing, B2B and Consumer Retail.

Our focus was to work, share and create usable output on the “Player Coach” level. I.e the leadership level set to champion, lead and drive the journey to get things successful in operations and scale with deep adoption within their organizations.

This is what went down, what we experienced and where to go from here.

The day was split into networking and three main co-creation sessions to address the first key questions that needs answer to get off the ground with a long term thriving and value adding Alliance, co-created by all in the room.

Session One: Set out to together explore the key challenges and capabilities we all need on operational level to become DAIR. The output is an Alliance backlog of EPICS, FEATURES and USER STORIES that all organizations in the room felt they need to work on at home, that also would be appropriate to collaborate on and share together as Alliance Open Source IP, checklists, process, methods, role descriptions, trainings etc. The Epics, Features and User Stories will after the event be compiled and posted on the Spring Co-create Slack Channel open for the participants.

Session Two was focused on allowing everyone in the room to experience the power of peer-to peer co-creation and learn by doing.  Grundfos was at the center of attention leading the session. They had brought two operational topics for all to work on that sits urgent on their agenda.  A) To nail down the key roles, responsibilities, tasks and KPIs of the Agile and Business lead cross functional Dev/Ops team to be  used as best practice in Grundfos globally for Analytics and AI. Secondly  B) We worked on the checklist and principles to be used to drive a Venture Cap inspired Use case life cycle approach to go from Idea that scales to Production. The detailed focus of the discussion was centered around driving the tasks that allows Grundfos use case by use case to create robust, compliant and secure re-usable raw data-, data pipeline- and algorithm assets, accelerating innovation and scaling by being able to drop things created by one team for one use case into another use case team.

Session Three was centered around co-creating on the format and focus of the Alliance for the first 12 months. We answered questions such as.  At what collaborative depth should we run the Alliance, what type of collaboration and co-creation do we seek. We discussed the range from simple knowledge sharing, co-creating of operating procedures all the way to an Alliance open source GitHub code repository.

Next we discussed which from all the epics and topics identified during the day we should focus on in the first Sprint of the Alliance. What topics was the preference of the alliance to start working on. We were able to boil down a short list of topics that came first on the agenda for many in the room.

All up. I think all in the room could feel the energy of peer-to-peer co-creation and learn by doing together with some of the best. Each session was almost impossible to break, because of the intense discussions and engagement and focus to get the workshop task done. We love when that happens…

In addition, we did a hybrid set up with one co-creation team being online with people from Canada, Germany, Denmark and south Sweden.  Which required careful execution and smart use of different technologies in the room. A combination of Google Meet, Phone and use of Slack to through out the day post the result. Hectic but fun. Keen for feedback how to improve, or if it worked as it was.

The follow up will be to compile all results and come up with the plan for the next 90 days. Tentatively:  

  1. Create a Backlog of Epics and features the Alliance want to work on.
  2. Boil down the input on how we want to work in a calendar of activities and potential open master classes.
  3. Frame the first topics we will work on in the first Alliance sprint from our short listed features.
  4. Get Bilateral input on the operating model and business model that the Alliance will start off with.
  5. Open up the first Epic to be worked on in the alliance to decide which two to five organizations and which experts will take the lead and work in the first sprint.
  6. Set a date for the next full Alliance Co-creation session. Where we will do knowledge sharing, review, retrospective and second iteration improvements on the work the first Alliance work group has worked on in the first Alliance sprint.
  7. Confirm who want to stay in and who want to join later, now with more clarity on the operating and business model of the Alliance.
  8. Execute the sprint.
  9. Prepare and execute our Autumn Co-Create session (Our 2nd Alliance event)

From the bottom of our hearts. Thanks for a great experience, and the feeling we could be on to something, but it is a journey we need to make together.  I hope in the end to create that we are all owners of this Alliance together, it is up to the Alliance as a group what we want to make out of it. Just tell us and we make it happen, is where we are coming from.

Please give us feedback, any comments or questions you might have!


Henrik Göthberg




Write a response … Close responses

Leave a Reply

Your email address will not be published. Required fields are marked *

Catch a cookie!

This website uses cookies to help improve your user experience.