21st century work-life has many differences from the traditional paradigm, and one of these differences is the many ways we can use technology to make our work visible to others.  Even when we’re working remotely the internet can remove the walls, and we can decide consciously whether and at what point our work will be of value to others if we choose to share it.  It’s all about visible teamwork – and the way this has evolved from ‘working out loud’, to become something far more deliberate and conscious. We are used to this as an internal concept, how we share with one another (and we’ll explore this in far greater detail when we bring you our special series on ‘Thinking Remote’ and our upcoming training course). But what about how we share publicly, when our sharing becomes part of our brand expression and content dissemination? Even when we’re recording our podcast, we’re talking about our work with an awareness that there’s an audience, a third party to the conversation, which brings qualitative differences to how we think about and discuss what we are working on… Someone who has been "working out loud” https://blog.freistil.it/working-out-loud-doesnt-mean-being-noisy-c71010e0d236 in the team for a long time, and since evolved the practice to share outside of his organisation is Jochen Lillich, from Freistil.it. (Pilar actually recorded this last year, but he’s only doing more of it now!). 14.08 The voice behind the blog: Jochen Lillich https://blog.freistil.it/turning-working-out-loud-to-11-live-coding-on-twitch-7dface39203e Friestil is the German word for ‘freestyle’, and his blog post explains how Jochen came to be livestreaming his work on Twitch, about as ‘out loud’ as you can possibly work. Twice a week at fixed times he does his coding in public, narrating in real time as he does the work, and also managing a live chat about what he’s doing. It’s like a screencast, but completely live and unedited, radically transparent. As a gamer, progressing from recording for internal use to livestreaming publicly felt like a natural transition for Jochen, and reflects Freistil’s transparency values – as coding is an unpredictable environment, things don’t always go to plan. The community - whose numbers grow steadily – can even suggest and help out when things get stuck, and Jochen feels strongly that his work has improved as a direct result of this regular broadcasting. Committing to the twice-weekly slots creates structure and accountability as well as a learning environment - an interesting solution perhaps, to the discipline issues some people struggle with when working from home… As well as weekday sessions, Jochen is also live coding on Saturdays 3.30pm, to reach people who can’t make sessions during the working week.  Tune in here if you’re curious to see Jochen in action! https://www.twitch.tv/fullstacklive _________ So how else could this kind of radical transparency be used to make our work visible? Maya is the first to admit that as an introverted writer, she couldn’t imagine anything worse than ‘writing out loud’ in this way (and declined Pilar’s challenge to try it!).  But Jason Fried from Basecamp has done just this and created a Youtube channel called ‘Getting Real – how we work at Basecamp’ https://www.youtube.com/channel/UCdx5Dk3EWTe2i8YDA7bfl6g (their podcast Behind the Scenes https://rework.fm/go-behind-the-scenes/ is also a great example of their approach).  Maybe it naturally suits certain industries, like the very open-source based software industry, to work in this way - though it obviously can work for collaborative writing projects. But at what point could ego get in the way and offset the benefits the Hawthorne effect (where we raise our game because others are watching) brings to the situation? Lots to consider… But sharing this way can only increase informal learning within the organisation, not least as it provides a focus, for watching and conversation (we found evidence for this in “Non-formal lea