Architects don't write code. That's the first thing that a developer notices when he or she moves into this job. But there is another change... substantial yet subtle... Architects don't accomplish anything without having someone else 'doing the real work.'
This is not that different from project managers and development managers. You have to move from the individual contributor role to that of leader and, to an extent, manager. However, this is not leadership by "I said so." Very few developers report directly to an architect. This is leadership by, well, leadership. You have to influence the decisions of others without having direct control over them.
Since you have no direct control, Leadership skills matter a great deal to the architect. You have to show that the team has common goals, and sell those goals. You have to share ideas, build credibility, set a direction and help each person to know how they can help the team to reach it.
Find the passionate among you. Most people are passionate about something. There is some aspect of their job that they love. Find it. Speak with them. Go to lunch. Share ideas. Brainstorm. Listen.
Find their passion and harness it. Show them how their passion can become their job. They will follow you into battle if they believe in the goal and their role in it and are passionate about their role. Developers will follow if they believe you can lead.