You need to learn/improve * Persuasion * Negotiation * Planning Besides hard skills these seems the most important ones. I have seen good technical architec

You need to learn/improve * Persuasion * Negotiation * Planning Besides hard skills these seems the most important ones. I have seen good technical architects being bad architects because: * They can't convince anyone that the ToBe architecture is worth it so any change has to be forced. This leads to a bad environment and overall lesser results. * They can't negotiate other teams'/business' goals with the ToBe architecture goal so, again, the ToBe architecture can be only forced to the teams. * They can't plan what is required to go from AsIs to the ToBe architecture. They can't tell you what's the most important change to be made, what should be done first and should be done in what order. This usually leads to an NobodyWanted architecture because random changes are being done.