Skip to content

Product : Interactive DevSecOps Playbook - Ideation

This is my (@fsieverding) Proposal for a concept of a deliverable on this KR. Please watch this video, me trying to explain my idea of what we could provide as a Landing Zone for customers, CSMs and other interested Parties.

What are Landing Zones?

Landing Zones are tailored environments designed to onboard and guide customers through their journey with a product or service.
They serve as a central starting hub, providing customers with actionable instructions, all the necessary resources, documentation, and guidelines to ensure a smooth and successful experience.
These landing zones offer a structured framework for customers to access vital information, engage with relevant support materials, and generate value as soon as possible out of their Product Usage. To create an effective Landing Zone, we must first understand our target audience.

  1. What are our customers' goals and objectives?
  2. What challenges do they face?
  3. What information and resources do they require to achieve their desired outcomes?

For us this will mean:

  1. Define Clear Objectives: Let us begin by clearly defining the goals of the landing zone. Determine what outcomes we aim to achieve. Align these objectives with the overall business strategy.
  2. Segment and Personalize: Customers have diverse needs and preferences. We will segment our customer base and personalize the landing zone experience accordingly, plus provide targeted resources and guidelines that address specific customer challenges, ensuring relevance and engagement.
  3. Intuitive Navigation: Our goal is to design a user-friendly interface with intuitive navigation that allows customers to quickly find the information they seek, by Utilizing clear categorization, search functionality, and logical content organization to enhance usability.
  4. Comprehensive Documentation: We have to offer comprehensive documentation, including user guides, tutorials and FAQs, presenting information in a concise and easily digestible format, leveraging visual aids like videos.
  5. Continuous Improvement: Our long term goal is to regularly assess and improve the landing zone based on customer feedback and product updates. Using this external and internal feedback to refine content, address pain points, and identify opportunities for enhancement.

Business Outcomes and Generated Value:

Implementing effective Customer Landing Zones can yield substantial benefits for both the company and its customers. Starting with this first Iteration will lead to…

For the company:

  • Increased product adoption and usage
  • Reduced customer churn rates
  • Improved customer onboarding efficiency

For the customers:

  • Streamlined onboarding and adoption processes
  • Access to comprehensive resources and support materials
  • Increased product knowledge and proficiency

Proposal: The GitLab DevSecOps Playbook

The Product will be a landing page for an enduser where they can choose with several drop down menus curtain parameters out of which then a list of items is displayed.
The Parameters with their possible values are:

  • GitLab Instance Type : {Self-Managed, SaaS}
  • Subscription : {Free, Premium, Ultimate}
  • Job Role : {GitLab Admin, Security Lead, Development Lead, DevOps Lead}
  • Size of Company : {Commercial, StartUp, Enterprise}

Then a list is displayed with filtered items which have the following columns:

  • Name : "Name of List item" [This is automatically a link to the corresponding subheading]
  • Description : "Description of List item"
  • Priority : Integer Values from #⃣ 1 to #⃣ 10
  • Implementation Difficulty : {easy, medium, hard}

Underneath the list in subheadings all list items with their detail views are displayed:

  • Implementation guide : "Long Text with links describing how to implement the feature in GitLab"
  • Demo Video Link : "Link to Demo Video how to implement and use the feature"
  • Link to internal Demo Project : "A link to a public Demo GitLab Project"

This all sourced out of a dataset with each dataset having the following attributes:

  • GitLab Instance Type applicable : {Self-Managed, SaaS, Self-Managed/SaaS}
  • The minimum Subscription : {Free, Premium, Ultimate}
  • List of applicable Job Roles : [GitLab Admin, Security Lead, Development Lead, DevOps Lead]
  • List of applicable Sizes of Companies : [Commercial, StartUp, Enterprise]
  • Name : "Name of List item"
  • Description : "Description of List item"
  • Priority : Integer Values from #⃣ 1 to #⃣ 10
  • Implementation Difficulty : {easy, medium, hard}
  • Implementation guide : "Long Text with links describing how to implement the feature in GitLab"
  • Demo Video Link : "Link to Demo Video how to implement and use the feature"
  • Link to internal Demo Project : "A link to a public Demo GitLab Project, which enables the production of the Demo Video and every GitLab CS Asset to run the Demo as well as the enduser to test it"

In the Background for each point in the GitLab DevSecOps Playbook is a Project repository to run a Demo and create the Video Tutorial.

Call to action

  • Give direct feedback on this idea.
  • What do you like about the concept?
  • In which aspect can it be better?
  • Have you seen something similar in the GitLab Handbook or documentation from which we can borrow a boring solution?
  • What would you see as best concept to deliver the content of our concepts?
  • What content could you adapt to bring into this deliverable?
  • Would you be on board with this concept as contributor?
  • What is the best place for the slides, demos and Videos to be stored and Maintain?
  • What are your ideas to keep the maintenance of all the pieces active?

Next Steps

  1. Define the deliverable?
  2. Define the scope of the first iteration? (static List with Demos and Videos in the Background, later the dynamic part?)
  3. Deliver on content.
  4. Define Maintainers.
  5. Define Contribution Guidance.
  6. Ideate and plan on next steps
Edited by Falko Sieverding