Advices to managers who start working in the open.

1. Transition from corporate
(closed) to open (source)
environments…
for managers
OpenExpo Europe Virtual Experience
17 de Junio de 2020
Málaga, ES
Agustín Benito Bethencourt
toscalix@gmail.com
CC-BY-SA 4.0

2. About toscalix

3. @toscalix
● Experienced manager in open environments.
● Consultancy/management on creation of complex Linux-based
systems/platforms/distros/products.
● Contributor in several FLOSS communities (KDE, openSUSE…).
● Worked at known FOSS orgs. like Linaro, SUSE, ASOLIF,
Codethink…
● Currently at Daimler Global Services Madrid for MBition.
● More about Agustín at his site.

4. 1. Why this topic.
2. Challenges.
3. Face the challenges.
4. Takeaways.
Talking Points

5. Let’s start!

6. 1.- Why this topic?

7. ● Everything started back in 2017 when introducing
young managers into FOSS projects.
● I had to explain the same topics several times.
● I did a recipe. It did not work well...
● … so I decided to write an article about this transition.
Why this topic?

8. ● I ended up writing 2.
○ Dear software manager, working in the open for the very
first time? Challenges (I)
○ Dear software manager, working in the open for the very
first time? Face the challenges (II)
● Later did consulting/advising on this topic.
Why this topic?

9. Please keep in mind that …
● … this is the result of my own experience and
conversations with others. It might not apply to you.
● … my main motivation is learning from others. I still
haven’t figured it all out.
Why this topic?

10. 2.- Challenges

11. 1. Open/public vs closed collaboration.
2. FOSS project vs product/service nature.
3. FOSS vs corporate culture.
4. Other challenges
Challenges

12. 1. Distributed and multicultural environment.
2. Asynchrony by default.
3. Documentation vs meetings.
4. Information and communication management:
restricted/confidential vs open/shared.
5. Who do you represent?
Challenge: open vs. closed

13. 1. Commodity vs differentiation: the 80% / 20 % rule.
2. Unique relation with other orgs and their staff: peers.
3. Delivery: release when ready.
4. Decisions: who pays your salary vs. the commons.
5. Definition of success.
Challenge: project vs.
product/service

14. 1. FOSS projects might be very different.
2. Most valuable leadership areas: technical first, then
people.
3. Radical approach to code/information ownership.
4. Standardization through adoption: influence
5. Consensus
Challenge: FOSS vs. corporate
culture

15. 1. Ethos.
2. Reputation.
3. Offline vs online personality.
4. Developer vs team as key/minimum execution unit.
Challenge: others

16. How to face the challenges?
1. Focus shift: from autonomy to alignment.
2. Definition of success: steer to maximise impact.
3. Rethink your goals, role and responsibilities.
4. Habits change mindsets: embrace new habits.
Face the challenges

17. 4.- Takeaways

18. Be aware of the journey. It will take time to master.
Takeaway 1

19. Everybody can succeed as manager in the open but it is
not for everybody.
Takeaway 2

20. It is a highway for personal and professional growth.
Take it!
Takeaway 3

21. Thank you
Agustín Benito Bethencourt
@toscalix

22. Q&A