Everyone loves a great documentation but no one loves to create one

Documentation fails because we miss to work on it. On our todo-list it usually moves automatically to the bottom. โ€œI can do this laterโ€.

Here are some tips to write a documentation:

๐Ÿ–– Small and steady – obvious thing. Reserve 30m every week to extend and refactor the documentation.

๐Ÿงžโ€โ™€๏ธ In the process – For tracking implementation it helps to have a process how you extend the tracking: New product feature -> Tracking plan for new feature -> Documentation

๐Ÿ‘‘ Share the results – Your big moment comes when someone asks you via slack about a specific data item (events, tables) and you simply send them the link to the docs. 

๐Ÿฆ Promote it – Every data team needs an internal newsletter, podcast, channel – use these channels to promote new documentation pieces.