A mentor of mine coined "BLAST" in to describe the "perfect blend" of the five core attributes he wanted for his role and responsibilities as he became an architect and progressed up the technical career ladder. I want to write it down before it gets lost. What follows is his framing.
While you may have a different view of your career and desired responsibilities, this is a good starting point for any senior lead, engineer, or architect.
Business. Involvement in the business process of software projects. Analyze and solve business problems through innovative technical solutions. Help identify business and revenue opportunities. Work as a bridge between "pure technical" and "pure business" organizations by being able to work with both types of people and communicate effectively with each type of audience. Client and customer interaction is key.
Leadership. Setting direction, team leadership, and decisions. Organize the development efforts of a project. Perform planning on the technical side. Act as thought leader, design leader, and have overall technical responsibility for projects. Role similar to the conductor of an orchestra. Exploring the managerial and people leadership role.
Architecture. Concentration in solving "problems in the large". Focus on large-scale and difficult technical problems. Solve problems at the fundamental level. Develop and use breadth of knowledge to solve multi-disciplinary problems. Doing the practice of architecture and effectively communicating architecture.
Strategy. Be a thought leader in how to anticipate and take advantage of changes in the technology climate. Be an influencer on projects, setting and reacting to overall broader company strategy. Work as a parallel yet intertwined technical counterpart to the business strategy organization. Perform critical evaluation of new technologies and trends. Identify new technologies on the leading edge and become knowledgeable one year before mass adoption, giving the company a competitive edge.
Technology. There are two parts to this. One is to be a successful practitioner. Rapidly absorb knowledge and evaluate and effectively use new tools and technologies. Stay current and broadly informed. The primary focus of the role should be technology but not necessarily "development". The second is technology leadership. On a practical level, be a mentor and be perceived as expert, help others increase their skills, teach where appropriate, write technical papers and articles, help develop and contribute to the company's total knowledge and expertise. Gain deep technical knowledge for key products and/or technologies, in addition to broad but shallower general knowledge in other areas.
Summary. A good amount of client interaction, combination of business and technical involvement, technology and thought leadership, team leadership migrating to the challenge of managerial responsibilities, strategic and practical involvement with emerging technologies. A focus on technology. However "developer activities" (coding, debugging, etc.) should generally be a smaller share of tasks except during technology investigation.