You like the company, and would want the tools get better. I bet the lead can vouch the same. But the tools break too often. Track it! And make it visible to e

You like the company, and would want the tools get better. I bet the lead can vouch the same. But the tools break too often. Track it! And make it visible to everyone both devs and non-devs. Especially non-devs, as they are likely the users to face the problem. I would propose/demo an issue tracking system, that would quantify the failures, and the amount of time it takes to resolve. It's on the 'best practices' list and is familiar to all, your lead may indeed agree. It's a team effort, eventually the team would come to realize how to proceed - rewrite or not, reshuffle the lead or something else. Make it visible for everyone, then your're not alone. BTW, management loves when things are tracked, as it makes their blame job easier, but it is a good team tool too.