2 ms·
Yes, I understand that. There is always a good reason as to why. I’m listening and measuring before we make changes. It’s not documented and if it is, it’s not
by Atotalnoob 3y ago
Yes, I understand that. There is always a good reason as to why. I’m listening and measuring before we make changes.
It’s not documented and if it is, it’s not surfaced in an easy to consume way. It doesn’t matter how good your docs are if they aren’t easily accessible.
I totally agree with you, though. The new guy shouldn’t change anything for the first X time. And I won’t. I’m just developing a roadmap for the future which will change and adapt.
- codingdave 3y agoI think documentation is a great example - the problem is not "nothing is documented", or even the accessibility. The problem is "lack of documentation causes X". Once you establish the business pain caused by the technical shortcomings, you have a list of "Xs", and can prioritize based on the level of impact of each. Then you come across as someone really looking to help and improve the organization, and not as someone just pushing personal preferences.