WIP: Added a link off the Solutions Architect page to a new page that outlines a...

Why is this change being made?

To outline a minimally viable process to capture SA activity on a weekly basis that will also promote the following:

• Transparency Providing an easy way for other team members to see a consolidated summary of all SA activity allows for questioning our actions and increasing the accountability of our execution. Transparency also promotes valuable collaboration.
• Collaboration Timely feedback can be provided by reading through a weekly summary. Team members may have experienced similar customer situations in the past and can offer an alternate perspective or guidance as an asynchronous comment. It's also easier to perform pattern matching across our plays by reviewing current activity. Finally, it's an excellent vehicle for team members to say thanks to those that have helped them with their activity and to receive recognition for work well done.
• Efficiency When team members have questions on how specific account activity went, they can read the weekly summary instead of seeking out the account team members. Leadership can make important decisions on how to run our business by parsing and reporting on weekly activity reports.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the change relates to any part of the project other than updates to content and/or data files (e.g. team.yml) please make sure to ping @gl-static-site-editor in a comment for a review and merge.
  • If the DRI for the page/s being updated isn't immediate clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies

For help with failing pipelines reach out in #mr-buddies in Slack