Skip to main content

Expectations

  • Common expectations of the systems architect role from stakeholders.
Meeting

Responsibilities and Expectations​

“Simplify technical complexities for each customer.”

Architect Responsibilities​

  • Providing architecture expertise while working collaboratively
    • Working with stakeholders to design and deliver technology solutions that meet business needs.
  • Defining the overall technical architecture
    • Taking into account factors such as scalability, performance, security, and maintainability.
    • Knowledge of current architecture, state, possible future state, and the ability to communicate the differences.
  • Identifying and evaluating different technology options and making recommendations
    • based on the organization's specific needs and constraints.
  • Collaborating with stakeholders such as business leaders, developers, and other IT professionals
    • Ensure that the solution aligns with the organization's overall strategy and goals.
  • Communicating the solution architecture and
    • ensuring that all parties understand and agree to the design.
  • Managing the implementation of the solution
    • Ensuring that it is delivered on time and within budget.
  • Providing ongoing support and guidance
    • Ensure the solution remains aligned with the organization's evolving needs.

Company Expectations (in their words found online)​

Some of these phrase are found often in solutions architect role expectations, as stated by hiring companies.

  • "Provide architecture expertise while collaboratively working with stakeholders."
  • "Facilitate and assist with efforts to define the future state of the enterprise."
  • "Provide clear guidance and assistance on moving from current state architecture towards the future state with roadmaps/runways."
  • "Ensure effective governance of defined industry and company software practices and standards".
  • Demonstrate and create prototypes, build reference architectures and define other effective solutions.
  • Continually stay abreast on current industry trends and lead the research and development efforts accordingly through proof of concept implementations, workshops, etc.
  • "Provide guidance, coaching and effective assessments for various IT teams and initiatives."
  • "Create prototypes and demonstrate innovative and effective solutions that align with organization’s objectives and maintain competitive market advantage."
  • Collaborate with various IT groups in continuously creating and modifying technology standards and practices.
  • "Champion product design, solution design and industry best practices while delivering software."
  • "Effectively communicate using written and oral presentations"
  • "Aid in the development of RFP responses, proposals, and Statements of Work ensuring customers’ needs are met, cost model is adequate, and deliverables meet sales and customer expectations."
  • "Identify key technical and business risks associated with solution designs"
  • "Present solution proposals to customers in collaboration with Sales."
  • "Lead technical engagement with vendors for products and support issues."
  • "Define all aspects of development from appropriate technology and workflow to coding standards."

Provide architecture expertise while collaboratively working with stakeholders.​

  • Demonstrate understanding of the company’s objectives and goals and create an architecture plan to support them
  • Engage with stakeholders from all areas of the business and IT to ensure the plan meets their needs
  • Work collaboratively with stakeholders to ensure the architecture plan is comprehensive and meets all of the business requirements
  • Develop and maintain relationships with stakeholders to ensure alignment with company objectives
  • Utilize best practices and industry standards when creating the architecture plan to ensure it is effective and efficient
  • Evaluate and monitor the architecture plan to ensure it is meeting the company’s objectives and is up-to-date with any changes in the business or IT environments
  • Identify potential risks to the architecture plan and develop solutions to mitigate them
  • Communicate regularly with stakeholders to ensure they are aware of progress and any changes to the architecture plan

Design a Solutions Roadmap​

  • Start by understanding the current state of the architecture and identifying the key issues or areas that need to be addressed.
    • Assess the current systems, applications, and infrastructure, and identifying any limitations or pain points.
  • Define the desired future state architecture by identifying the business and technical goals that need to be met.
    • Identify the key requirements and objectives of the new architecture, such as scalability, performance, and security.
  • Identify the key initiatives and projects that need to be undertaken in order to achieve the desired future state architecture.
    • Identify the systems, applications, and infrastructure that need to be implemented or replaced, and the dependencies between them.
  • Create a high-level roadmap that outlines the key initiatives and projects, and defines the overall timeline for the transition to the future state.
    • This roadmap should also include the key milestones that need to be achieved, such as the completion of specific projects or the implementation of specific systems.
  • Break down the high-level roadmap into smaller, more detailed roadmaps that outline the specific steps and tasks that need to be completed for each initiative or project.
    • Identify the resources required, the dependencies between tasks, and the expected completion dates.
  • Continuously monitor and track progress against the roadmap, and make adjustments as necessary.
    • This includes identifying and addressing any issues or delays, and communicating progress and status to stakeholders.
  • Once the future state is achieved, review the process and results and make any necessary adjustments for future improvements.
  • Enterprise roadmap info and examples: