I am really curious about setting up anonymous web analytics with adblockers and cookie consents. Because with Google Analytics I really have struggles to get consistent insights into my web analytics.
I voted for "managing and delegating", though I'm curious about "documenting processes" because to me that seems like a really big waste of time in the early days since the processes will almost certainly change drastically.
A very personal opinion, but I think as many things in life it is about building habits.
My background is development even if I am looking for a transition into entrepreneur, technical writer, engineering visualization expert.
That being said, I think documentation can have a big impact on the time it takes to develop an idea if you are not a developer, practices makes perfect and documentation is an exercise of explaining others. If you are a developer I still think is a great way to spare some time to think about the architecture and simplify external evaluation/validation.
I agree process will change drastically, but often I think that will never stop in a growing company no matter how big it is, and it is easier to build docs incrementally than to start from the ground once users start asking it. But you can start with hints, more as a note-taking exercise and then if the project succeed add very detailed explanation for the hard parts and diagrams.
Thanks for the explanation! I'm guessing that much of the benefits are with larger teams? For a solo founder or two co-founders, would you also use the same approach?
Starting incrementally with notes makes sense too.
Definitely! Benefits are more as team size increases, but it is hard to say in an early stage if the team will ever increase so I feel it is a good idea to have a very lightweight process in place even as solo founder.
Love this whole conversation and completely agree - the amount of time you put into documentation should be proportionate to how big your team is and how detailed your processes are (to start with they're literally just a checklist of steps with no explanation and that's great!)
They will absolutely change and evolve, but one of my major arguments is that from experience, having the written process actually helps you analyse and iterate on it, especially when you have a process that mostly works but there are a few steps which could be optimised.
Post coming today, so hopefully that will expand on it!
Thank you so much! I'll be sure to reply to this post when I have put the next one up - asked in a few places and documenting was the front runner so watch this space!
UPDATE: here is the documenting processes blog (part 1) I'd love to know your thoughts!
I am really curious about setting up anonymous web analytics with adblockers and cookie consents. Because with Google Analytics I really have struggles to get consistent insights into my web analytics.
I voted for "managing and delegating", though I'm curious about "documenting processes" because to me that seems like a really big waste of time in the early days since the processes will almost certainly change drastically.
A very personal opinion, but I think as many things in life it is about building habits.
My background is development even if I am looking for a transition into entrepreneur, technical writer, engineering visualization expert.
That being said, I think documentation can have a big impact on the time it takes to develop an idea if you are not a developer, practices makes perfect and documentation is an exercise of explaining others. If you are a developer I still think is a great way to spare some time to think about the architecture and simplify external evaluation/validation.
I agree process will change drastically, but often I think that will never stop in a growing company no matter how big it is, and it is easier to build docs incrementally than to start from the ground once users start asking it. But you can start with hints, more as a note-taking exercise and then if the project succeed add very detailed explanation for the hard parts and diagrams.
Thanks for the explanation! I'm guessing that much of the benefits are with larger teams? For a solo founder or two co-founders, would you also use the same approach?
Starting incrementally with notes makes sense too.
Definitely! Benefits are more as team size increases, but it is hard to say in an early stage if the team will ever increase so I feel it is a good idea to have a very lightweight process in place even as solo founder.
Love this whole conversation and completely agree - the amount of time you put into documentation should be proportionate to how big your team is and how detailed your processes are (to start with they're literally just a checklist of steps with no explanation and that's great!)
They will absolutely change and evolve, but one of my major arguments is that from experience, having the written process actually helps you analyse and iterate on it, especially when you have a process that mostly works but there are a few steps which could be optimised.
Post coming today, so hopefully that will expand on it!
👍
This comment was deleted a year ago.
Thank you so much! I'll be sure to reply to this post when I have put the next one up - asked in a few places and documenting was the front runner so watch this space!