Engaging a Solutions Architect

When and How to Engage a Solutions Architect

Engaging GitLab Solutions Architects

Before getting SA involved:

1) Qualification:

2) Preparation:

Help us, help them. 3 ASKs:

The SA should either be included in a discovery call or provided with Outcome / Infrastructure / Challenges (see below) information uncovered by the AM in prior interactions with the account. Occasionally, we could support a combination call of discovery and technical demonstration/deep-dive, but this is suboptimal. However, the latter approach does not allow the SA time to prepare for and/or tailor the discussion.

Outcome WIIFM/T. What’s in it for them? Why are they looking at a new strategy for s/w dev. We need to be able to tailor our demos and presentations to demonstrate value and how we can address their issues.

Infrastructure What i2p tools do they currently have in place? E.g. Jenkins for CI, Ansible/Chef for automation, Codebear for review, VS/eclipse/emacs/vim for dev, etc.

Challenges What problems/roadblocks are they having? Release velocity, visibility, collaboration, automation.

3) Engagement Protocol:

First, Navigate to the SA Service Desk Board here

NOTE: The board is located in the Group “Customer Success” and the name of the project is “SA Service Desk”

  1. Create a new issue
  2. Use the "SA Activity" template to ensure the proper data is collected about your needs
  3. Add the “SA Backlog” label to the Issue
  4. The SA Team will triage the SA Backlog queue and collaborate with the submitter via Issue Discussions.

NOTE: This will not replace SFDC. The SAs will still be required to input the necessary information for each account that is critical to the strategy