Create guidelines and recommendations for Remote Design Sprints

Why is this change being made?

The Configure team has recently hosted a cross-stage design sprint focused on the new vision for Auto DevOps.

That experience led to lots of learnings around the Design Sprint benefits, limitations, and opportunities for process improvement (see the feedback issue).

It also showed that the classic Design Sprint process has to address the limitations and leverage the benefits of being remote and spread across the time zones.

The practice of Design Sprints at GitLab is new, and we should document what we learn and continuously iterate on these guidelines to offer an effective tool for problem solving at GitLab and across other distributed/remote organizations that might want to give Remote Design Sprint a try.

This page can be linked in the UX handbook pages as a tool for cross-stage and cross-functional ideation on big and hairy problems, when the ThinkBig format is too lean for the problem scope.

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 DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
  • 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.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)