Change your job, or change your job.<p>You could discuss how the lack of documentation is causing the team issues; maybe even frame it in a way to highlight how documentation will make him more useful (more time to spend on architecture vs answering questions, better chance that his architecture will be implemented as designed).<p>Express your concerns about introducing new technologies -- something that I&#x27;ve had some success with is asking &#x27;which library&#x2F;framework&#x2F;dependency will we able to remove if we add this new one?&#x27;. Propose that the architect allocate time to training the team or being on pager duty or fixing maintenance bugs if they feel strongly that a new tech is the best decision.<p>If that doesn&#x27;t work and the situation is unworkable, then consider a move.